To move a birthday wishlist from notes, gather the wishes you already have into a working list, remove duplicates and outdated items, then add each wish manually to the new list. After saving, compare the meaning and specifications, not just the number of entries. Leave contacts, addresses and conversations behind.
This is for someone who has already collected wishes. It is not a gift selection or sharing guide, and it does not assume automatic import or synchronisation.
Prepare the source first
Notes capture quick ideas; a wishlist entry must make sense to someone who never saw your conversation. A short review prevents vague references and old links from moving into the new list.
Copy only the relevant wishes into a temporary private note. Do not copy whole conversations, phone numbers, addresses, order details or other people’s contacts. Keep the original notes until the comparison is complete.
Mark each entry “move”, “clarify” or “outdated”. Transfer clear wishes first, hold unclear ones for review and exclude those you no longer want.
Merge duplicates by meaning
“A tea mug” and “that white mug” may refer to one gift. Compare the item, model and quantity before merging. Two acceptable alternatives should not accidentally become two required presents.
| Source note | Decision | Prepared entry |
|---|---|---|
| One model recorded twice | Merge | One entry with clear specifications |
| “That thing from the chat” | Clarify | Name and purpose in plain language |
| Link plus a separate explanation | Combine | One gift with a useful comment |
| Something already bought | Exclude | Remove from the current list |
| Two acceptable options | Clarify | Explain the alternative without doubling the request |
For starting from scratch, see the separate wishlist planning guide. Here the aim is to preserve existing wishes.
Add each wish manually
- Open the prepared source beside the new list.
- Add a clear name, essential specifications and a short comment, without conversation history.
- If a link is needed, reopen a normal product page and check the model. Avoid order or account URLs.
- Save the gift and read the resulting entry again.
- Mark it checked in your working note and continue.
A price or stock note in an old message is not current evidence. Transferring text does not validate either. If the exact option cannot be found, keep a clear wish without promising availability, or set it aside for clarification.
From shorthand to a gift entry
An illustrative note says: “Travel mug, as discussed, 350, light.” After clarification: “Model A travel mug, 350 ml, light colour. Another colour is fine; capacity matters.”
This is an example, not a product recommendation. First establish whether “350” means capacity, price or a model code. The birthday gift description guide covers fuller wording.
Choose a home for the final list
One ordinary note works if you can maintain it manually and answer separate questions. A wishlist by link helps keep wishes together for guests.
The Osanta birthday workflow describes adding gifts, ideas and comments, sharing one link and showing gift statuses. Guests choose available items; the owner sees reservation status, not the giver’s name. This helps coordination but cannot guarantee no duplicates when purchases happen outside the list.
Start from the birthday page. The owner needs email and access after signing in; an already signed-in owner uses the current account. Add wishes manually. Do not assume automatic import, collaborative editing, synchronisation or preservation of old prices and stock.
Compare with the source
Read the final list beside the prepared note. Check each current wish’s name, model, size, colour, quantity, alternatives and link. Equal entry counts are not enough because duplicates may have been merged.
- Every current wish is moved or deliberately deferred.
- Duplicates did not become extra gifts.
- Shorthand is explained.
- Links and specifications were checked manually.
- Contacts, addresses, messages and order details are absent.
- Saved entries have been reread.
- The private source remains until comparison is complete.
After checking, treat the new list as the current version and make future changes there. Stop using old notes actively; decide whether to delete them only after the comparison.
Preparing a birthday?
Collect wishes in one link so guests can see available gifts and avoid duplicates.
Questions on this topic
Can I import the notes automatically?
This process uses manual entry. Automatic import, integration and synchronisation are not promised.
Should I move the whole conversation?
No. Move only the clear wish and necessary specifications, without contacts, addresses or message history.
How do I merge duplicate wishes?
Compare the item, model and quantity. Merge entries for the same gift; clarify different alternatives first.
Will an old price remain current?
Moving text does not verify price or stock. Check the normal product page manually rather than promising old conditions.
When should I delete the source notes?
Only after checking the final list, if you no longer need them. Keep the private source until then to avoid losing a current wish.