We make Listify, so this article is written by the app you would be moving to. It covers only what is particular to moving from Swym Gift Lists and Registries: the scope question Wishlist Plus raises, what we look for in a Swym export, and where each app is the better fit. The move itself is ours to run: free white-glove migration support, on any plan, from your export.
It is not a general migration guide. The full process, from requesting an export to switching over, is in the Shopify gift registry migration checklist, and this article does not repeat it.
1. The first decision: registries only, or the wider Swym setup?
Swym Gift Lists and Registries is one product from a company that also makes Wishlist Plus, and many stores run both. Before anything else, work out what you actually use, because that defines the real scope of the migration.
- Only Swym Gift Lists and Registries
- Swym Registry plus Wishlist Plus
- Shopify POS through Swym
- Address masking at checkout
- Custom fields or bespoke work Swym has done for your store
A store using only the registry app has a straightforward scope. A store leaning on Wishlist Plus, POS or a customisation has a decision to make about each one, and section 6 covers the Wishlist Plus part specifically.
2. Why a merchant might choose Listify
Swym and Listify solve overlapping problems in different ways. These are the differences that tend to matter to stores considering a move. You can evaluate Listify's storefront experience on the free plan; Shopify POS is available on the Pro plan.
Registries and unlimited wishlists in one app. One set of theme blocks, one subscription, and a saved wishlist item becomes a registry item later without the shopper starting again.
A multilingual storefront built in. The registry and wishlist experience ships in your store's languages, translations are included on every plan, and the Growth plan lets you rewrite the wording yourself.
Theme app block integration. On Online Store 2.0 themes, Listify uses Shopify theme app blocks without writing into the theme's Liquid, and the panel is isolated from your theme's CSS so neither can break the other. Vintage themes may require a generated snippet.
Appearance settings that follow theme changes. Colours, style and cover image live against your shop rather than your theme, so they survive a theme switch.
Guided setup and active support. The app reads your live theme and reports which blocks are present and switched on, and a real person answers when you write to us.
Free white-glove migration support. We run the move for you from your export, and check the catalog match, purchase data, custom fields and existing links before anything is switched off.
POS for buying from a registry. On the Pro plan, staff find an existing registry at the till by name or QR code, tag the basket items to it and take payment. Registries are built by the customer on their own phone, not by staff at the counter.
Swym also offers analytics, so that is not a difference between the two; both give you registry reporting in your admin.
3. When Swym may remain the better fit
We would rather say this here than have you find it out after moving.
Address masking is required today. Swym hides the recipient's shipping address from gift-givers at checkout. Listify does not. If your registries depend on that, this alone is a reason to stay on Swym, and we would rather you knew before planning anything.
You are happy with Wishlist Plus and want one provider. Two specialised products from one established vendor, with one support channel and one billing relationship, is a reasonable thing to value. Listify has no equivalent to that arrangement.
You rely on a Swym customisation. Custom fields or bespoke work Swym has done for your store may have no direct equivalent, and each one needs mapping or replacing before the move makes sense.
You have a Swym POS workflow that has not been replicated and tested in Listify. Swym's POS support unifies online and in-store lists. If your counter depends on it, test the Listify equivalent with a real registry before committing.
There is no specific problem to solve. If Swym already supports your workflow and nothing in section 2 is something you actually need, migration creates work without enough benefit.
4. What Listify checks in a Swym export
We still inspect each Swym export before confirming what can be preserved, because a store's file can differ from the ones we have seen. This is what we look for, and what Swym's exports have carried so far.
| Data | What Listify checks |
|---|---|
| Registry and event details | Whether they are included |
| Registrant and co-registrant details | Registrant contact details and co-registrant names; Swym's export carries no co-registrant email |
| Products and requested quantities | Whether each product matches a purchasable Shopify variant |
| Purchased quantities | Included per item and imported, so a half-bought registry stays half bought |
| Individual purchase records | Not in Swym's export, so the gifts arrive counted but without buyer names |
| Shipping details | Whether they are included |
| Custom fields | Mapped where Listify has a place for them; anything else is listed for you before you commit |
| Registry passwords | Not imported; a password-protected registry may get a new password, which we send you |
| Existing registry links | Forwarded through Listify's app embed when the export includes registry IDs, see section 7 |
| Wishlist Plus data | Not part of the registry export, see section 6 |
Registrant email and a reliable product identifier are the two fields that matter most for a migration to Listify. The migration checklist explains why, and what to ask Swym for when you request the file.
5. The purchase-progress question
This is the part of a Swym migration most stores ask about first, because it decides what registrants and their guests see the day after the move.
The registry records themselves are usually the straightforward part. Previously purchased gifts are the sensitive part: if a registry that was half bought arrives as unbought, guests who already gave get asked again, and registrants email you.
There are two different kinds of purchase information, and they are separate questions. Swym's export carries a purchased quantity against each item, and we import it, so a registry's progress comes across and nobody buys a duplicate. It carries no buyer names, so who bought each gift does not come across.
That is also what a registrant sees afterwards: the progress is right, and the gifts already bought carry no name.
If your file arrives without those quantities, we check whether previous registry purchases can be reconstructed from your Shopify orders. That depends on whether the orders can still be connected to the correct registry and product. If they cannot, active registries may lose their previous completion state, and that is the case where waiting for a quieter month is the right call. We explain the result before recommending a migration date.
6. What happens to Wishlist Plus
Nothing, unless you decide otherwise. Swym Gift Lists and Registries and Wishlist Plus are separate apps with separate data. A registry migration does not remove, change or touch Wishlist Plus, and its data is not part of the registry export.
That leaves three options, and all three are reasonable.
- Move the registries and leave Wishlist Plus unchanged. Plenty of stores do this and run Listify for registries alongside Wishlist Plus for wishlists.
- Move the registries first and assess wishlists later. Once registries are settled, decide whether Listify's included wishlists suit you, with no deadline attached.
- Consolidate both into Listify as one planned project. One app, one set of theme blocks, one subscription. This is a bigger decision than a registry migration and deserves its own scoping.
If you take the third option, Wishlist Plus data is a separate migration with its own export, and we scope it separately.
7. Existing registry links
A registry link your customer shared has your domain in it, but Swym serves it, so once Swym is removed the link no longer shows the registry by itself. Listify records real Swym registry links before anything changes. If Swym's export includes registry IDs, we keep them on each migrated registry and Listify's app embed forwards an old link to the new registry. If the export has no IDs, there is nothing to match an old link against, and registrants share their new link instead. We tell you which case you are in once we have seen the file, and Swym stays installed until the migrated data has been approved.
8. How the move works
There is no self-serve importer, because the move is ours to run: free white-glove migration support, from your export, while Swym stays installed and your registrants carry on using it.
- Install Listify and ask Swym support for the registry export, which arrives as a CSV. Ask for registry IDs in it: they are what let old links forward.
- Listify checks the catalog match, purchase progress, custom fields and link structure, and confirms the scope.
- Listify imports the registries and reports every exception, including where purchase progress or buyer details could not be preserved.
- You review and approve the result in your own admin before anything is switched over. Registry emails start switched off, so nobody gets mail about old activity, and we turn them on when you are ready.
The detailed sequence, including the switch-over order and what to tell registrants, is in the migration checklist.
Common questions
- Can active Swym registries be moved?
- Yes, and it is the normal case. Swym's export carries purchased quantities, so they arrive at the completion state they were at. We still check your file before recommending a date.
- Will purchased gifts remain marked as purchased?
- Yes. Swym's export carries a purchased quantity per item, and it comes across. Who bought each gift does not, because Swym's export has no buyer names.
- Must Wishlist Plus move too?
- No. It is a separate app with separate data, and a registry migration does not touch it. See section 6 for the options.
- Will registrants need to do anything?
- They sign in once with their email to manage their migrated registry, which arrives built, with items and quantities intact. A password-protected registry may get a new password, which we send you to pass on.
- Will address masking work the same way?
- No. Swym hides the recipient's shipping address from gift-givers at checkout, and Listify does not. If your registries depend on that, it is a reason to stay on Swym.
- Can staff still use Shopify POS?
- For selling from an existing registry, yes, on Listify's Pro plan. For anything your Swym POS workflow does beyond that, test the Listify equivalent with a real registry before committing.
- Must both apps remain installed temporarily?
- Yes. Swym stays installed until you have approved the migrated result, which is the part that makes the move safe. You will pay for both for the overlap. The migration itself is free on any plan; if you are bringing more registries than your plan includes, you will need a plan that covers them.
- How long does the migration take?
- It depends on the export, the catalog match rate, how many registries have active purchases, any custom fields and the number of exceptions. We confirm the scope after reviewing the export, not before.
See what your Swym migration would involve
Both apps publish their current pricing on the Shopify App Store. Compare the plans against the number of active registries you expect to run, particularly in your busiest season: Swym Gift Lists and Registries and Listify.
Send us your export before uninstalling anything. We'll check the catalog match, active purchase progress, registry links, custom fields and whether Wishlist Plus is part of the project, then explain the scope before you commit to moving. Get a migration assessment