The Shopify gift registry migration checklist

We make Listify, a Shopify gift registry app, and this is the checklist we work from when we move a store's registries across from another app. It is written so it is useful whichever app you are moving to, because most of it is about your data rather than about us.

Every migration depends on what your current app's export contains. That is why most of the steps below are checks rather than actions, and why a reliable timeline or migration commitment requires seeing the file first. Where something below is specific to how Listify does it, we say so. Where something still has to be tested on your store, we say that too.

The one rule that holds in every case: do not uninstall your current app until the data has been checked and the redirect file for your existing registry links has been imported.

1. Decide whether now is the right time

Before you email anyone, answer five questions about your own store.

• How many registries are active right now?
• How many of those have recorded purchases against them?
• How close are the upcoming events?
• How heavily is the registry used in store, at the till?
• Can your current app stay installed and running while the migration happens?

The more active your registries are, the more the rest of this checklist matters, and the more important it becomes that purchased gifts stay marked as purchased. A store with quiet registries can migrate in almost any week. A store in the middle of its season, with lists that are half bought and events three weeks out, should treat purchase history (section 5) as the question that sets the date.

2. Request the complete export

This is usually the longest part of the whole migration, and it is the part neither you nor your new app controls, so start it first.

Do not uninstall your current app until you have received the export, opened it and saved it somewhere that is not your inbox. After uninstalling you may lose access to the data entirely, or need help from the previous provider to recover it. Never depend on that.

Ask for:

• A registry identifier for each registry
• Registrant and co-registrant names and email addresses
• Event type and event date
• Product identifiers for every item: SKU, barcode, or the platform's own product and variant IDs
• Quantity requested per item
• Purchased quantities, or better, the purchase records themselves: order number, buyer, date
• Shipping address and phone where held
• Any custom fields or per-item notes
• Closed and past registries as well as active ones

Ask for the file raw. Tidying is where the column you needed gets dropped for looking redundant. A short, plain request works better than a long specification, which invites either a stall or a hand-curated subset:

We're moving our gift registry data and need a full export, ideally CSV or a spreadsheet. The essentials are: registrant name and email, event type and date, the items on each registry with SKU or barcode and the quantity requested, and anything already purchased off a registry, with order details if you hold them. Please send it exactly as it comes rather than reformatting or cleaning it up. If it contains more than the above, better still.

Two files joined on a registry identifier is the easiest shape to work with. One flat file with a row per item and the registry columns repeated is equally fine.

3. What can transfer

For a migration to Listify, two fields matter more than the rest. Registrant email is what attaches each migrated registry to the right Shopify customer, so its owner can sign in, manage it and see who bought what; a registry that arrives without one sits on your store unclaimable until the data is edited. A reliable product identifier, such as a Shopify variant ID, SKU or barcode, is what connects each item to a purchasable variant in your Shopify catalog. Most other missing fields can be reviewed as individual exceptions rather than preventing the entire registry from being imported.

Listify does not import passwords from another registry app. Registrants who used password protection will need to create a new one after the move, which is worth a short email (section 9).

Anything that is visible in your current app's admin but not in the file they hand you does not exist as far as the migration is concerned. That is why you open the export before making any promises internally.

4. Check the Shopify catalog match

Every registry item has to resolve to a real variant in your Shopify catalog to be purchasable after the move. This check is what turns a guessed date into a real one, and it is the step most often skipped.

A clean SKU in the export does not guarantee the product exists in Shopify. SKU format and catalog coverage are two separate problems: an export can be perfectly formatted and still fail, because the product was in the old registry system but was never fully synced into your Shopify store. In one migration we ran, this was the case for a meaningful share of the registry assortment, and it turned a migration into a catalog project first.

Product names are a weaker identifier than SKU or barcode. On a catalog with colour and size variants they are frequently ambiguous, and an item has to match one specific variant to be added to a cart.

Unmatched items are a merchant decision, not a technical one: add the product to Shopify, map it to an equivalent, or drop it from the registry. Ask for a plain list of everything that did not resolve, and decide before the migration runs rather than after.

5. Check purchase progress

When a guest buys something off a registry, the registry has to remember it, or the next guest buys the same thing. That memory is the part of a migration most likely to be lost, and the loss is customer-facing: guests who already bought get asked again, and registrants email you.

Purchase progress may be included in the export, or it may need to be reconstructed from your Shopify order data. If neither source provides enough information, previously purchased items may have to arrive as unpurchased, causing an in-flight registry to restart at zero purchased.

In Listify, purchased quantities are tied to order records rather than stored as a bare count, which is what lets a registrant see who bought what. A spreadsheet column saying "3 purchased" therefore has to become order records, and those can only be rebuilt where the purchase went through your Shopify store and can still be matched to the right registry and item. Some source apps export the purchase records themselves, which makes this straightforward. Others export a count, or nothing.

This is why purchase history sets your timing. If your registries are quiet, move whenever suits you. If they are half bought with events approaching, have the export and the order matching checked before you commit to a date, and expect heavily active registries to need closer inspection than the rest. Push hard for purchase records when you request the export: they are one of the most important parts of the file, and their absence is one of the migration problems your customers are most likely to notice.

6. Check existing registry links

A registry link your customer put on a wedding invitation has your domain in it, so it feels like yours. It is not entirely. Most registry apps serve their pages through an app proxy, a path on your domain that only resolves while that app is installed. Remove the app and the link lands on a blank page.

The fix is Shopify URL redirects, one per registry, from the old path to the migrated registry. Listify builds that redirect file from the old registry identifiers kept on each migrated registry, and you import it before the old app is removed. Once the redirects are in, an old link sends the shopper straight to the new registry with a permanent redirect. A link with no redirect behind it still hits a blank page, so the redirect file is what keeps links alive, and only once it has been imported.

• Record the old link format before anything changes: take real links from emails or invitations your store actually sent.
• Keep the old registry identifiers in the export. They are what each redirect is built from.
• Import the redirect file before the old app is uninstalled. The redirects stay inert while the old app still answers those paths and take over the moment it stops.
• After switch-over, open the real links you recorded in a private window and check each one lands on the right registry.

Shopify's documentation lists /apps as a prefix that cannot be redirected, which is where several registry apps live. In our testing the redirects resolve regardless, and we confirm it on your store rather than taking either the documentation or our own test on trust.

7. Run the migration while the current app stays active

Your current app keeps running through all of this. That is what makes the migration safe: existing links should continue to resolve through the current app while it remains installed and unchanged, and registrants carry on using the app they know while the work happens. Listify's storefront components remain disabled until you approve the result and choose to switch.

1. Import the registries into Listify from the export.
2. Review the exceptions: items that did not match, registries missing an email, purchases that could not be rebuilt.
3. Check several migrated registries by hand. Pick your most complicated one deliberately, not your simplest.
4. Confirm purchased quantities on two or three registries whose real state you know.
5. Configure how the widget looks on your storefront now, while nothing is live.
6. Walk the guest journey on a migrated registry: open it, add something, buy it if you can, confirm the registry updates.
7. If registries touch your counter, test the POS workflow with a real registry.
8. Approve the result before anything switches over.

8. Switch over

The exact sequence depends on your source app and on what the link check found, so treat this as the shape rather than a script.

1. Confirm the migrated data and the storefront configuration are approved.
2. Import the redirect file from section 6 while the old app is still installed.
3. Keep a permanent copy of the export. It is your essential recovery record if anything needs to be checked, corrected or reconstructed later.
4. Disable or uninstall the old app.
5. Enable Listify's storefront components: the app embed and the blocks you want on product, registry and account pages. Decide this before the day, not on it.
6. Test creating a registry and buying from one, as a guest, in a private window.
7. Test the old shared links you recorded in section 6.
8. Inspect the live theme for anything the previous app added: blocks, snippets, script tags or code. What Shopify removes automatically depends on how that app was integrated, so look rather than assume.

Plan the switch-over so the gap between the old storefront experience and Listify is as short as possible. Depending on the source app, it may be possible to prepare Listify's storefront components before uninstalling the old app; in other cases the final activation happens immediately afterwards. The exact sequence should be agreed once the old app's theme integration has been checked.

Timing overall depends on the export, the catalog match rate, active purchase history and the number of exceptions. Listify confirms the scope after reviewing the export.

9. Communicate only what customers need to know

A well-run migration is one most registrants never notice. Tell people what affects them and nothing more, because anything beyond that invites questions about a change they would otherwise not have seen.

• Registrants who set a password on their registry need to create a new one. A short email from you is much better than letting them discover it.
• Registrants may need to sign in once to claim their migrated registry. If someone cannot see theirs, the usual cause is an email address that did not match, and it is fixable while you still remember the migration.
• If a registry's old link is not covered by the redirect file, that registrant needs a replacement link to share, and they need it before their event.

Keep the redirects in place permanently; there is no way to know when the last guest will click a link from an invitation sent two years ago.

Before you uninstall anything

The single most common mistake is uninstalling before exporting, because uninstalling feels like the natural first step of leaving. It is the last one.

If you are moving from a specific app, there are separate guides for Gift Reggie and Swym covering what is particular to each export.

Get a migration assessment before uninstalling anything.

Send us your export and we'll check:

• What can be matched to your Shopify catalog
• What needs attention
• Whether purchase progress can be preserved
• What happens to your existing registry links

We'll explain the scope before you commit to a migration date. Start on the migration page