How to switch from Shopify without losing store data

Leaving Shopify? Protect product records, URLs and customer access, move the live store, then cancel the subscription after checkout and support checks.

To switch from Shopify, export your store records, build and test the replacement shop, then move the domain before cancelling your subscription. Shopify supports exports, but the new platform decides which fields it imports. Customer sign-in, app records and outstanding gift cards need their own transfer plan.

This procedure is for retailers leaving Shopify for another platform. Keep the old store available until the replacement handles purchases and your team can support orders placed before the move.

Decide what must survive the move

Define a successful move by the work your store must still do: accept purchases and fulfil both new and existing orders. Give one person responsibility for the cutover and another for customer support. The store owner must remain available for domain and subscription changes.

Separate the platform decision from the migration procedure. If the problem is one slow app or a missing product filter, fixing that part can avoid rebuilding a working shop. If a required selling workflow cannot run on Shopify, make that workflow a condition of ecommerce platform selection.

Write down every dependency before changing access. Include warehouse stock, payment providers, subscriptions, staff permissions, marketing consent and customer notifications. Decide which system will hold historic orders and who can issue refunds after the move.

Moving into Shopify is a different task. The Shopify migration guide covers that direction.

Export records before changing access

Export the records while your team still has permission to read them, then keep untouched copies separate from files prepared for import. A comma-separated values (CSV) export contains rows of data. A restorable backup also needs the assets, settings and a tested restoration method. A destination import only loads the fields its importer supports.

Use Products > Export for product records and Customers > Export for customer profiles. From Orders > Export, save the required order range and transaction history. Check that the exported range includes older paid orders with open returns or unfulfilled items.

Store transfer matrix

ItemSource materialFields to preserveLimits and manual workDestination acceptance check
Products and variantsProduct CSV and separate inventory export where neededProduct handles, variant options, stock keeping units (SKUs), prices and stockMap each destination field. Rebuild unsupported custom fields and collection rulesProduct and variant counts match the accepted records
MediaProduct image references and saved original assetsImage-to-product relationships, image order and alternative textCSV contains image references, not image files. Transfer other media separatelyImages load from the replacement store’s own storage
CustomersCustomer CSVContact details, addresses and consent fieldsPlan the destination’s account activation or sign-in process separatelyA test customer can sign in and sees only permitted records
OrdersOrder CSV and transaction exportOriginal order numbers, line items, payment references and fulfilment statusA readable export does not establish refund capability in the new systemStaff can locate an older order and its original payment
Issued gift cardsGift card export and balance recordsCustomer association and remaining liabilityStandard export includes only the last four code characters. Arrange supported replacement codes or another resolutionEach outstanding balance has a recorded treatment
URLsExisting redirect export and a list of live product and collection pathsOld path and equivalent new destinationRebuild redirects on the system serving the moved domainOld links reach the matching replacement page
Policies and app dataSaved policy text and each app’s supported exportDelivery rules, returns terms and required app recordsRecreate page layouts, app settings and unsupported recordsPublished policies and connected services match the intended rules

Shopify’s instructions for exporting products say images must remain publicly accessible while the replacement imports them. Keep the old products intact until the new store has copied the images. Avoid sorting the original product CSV, which can separate variants from their product or image references.

The gift card export guidance says the standard file cannot recreate cards in another system on its own. Reconcile outstanding balances before closing the source store. Treat customer credentials and app records as separate tasks rather than assuming the product import carries them.

Build and verify the replacement shop

Build the replacement in a private test environment before the final transfer. Use the destination’s official import format and redirect documentation for that platform. Its accepted fields and import tools determine how you prepare the exported data.

  1. Configure the destination store and give staff only the access their jobs need. Keep customer notifications disabled during trial imports where the platform supports that control.
  2. Map product handles and SKUs to the new product and variant identifiers. Record this mapping for stock updates and order support.
  3. Configure payment methods, tax settings and delivery zones. Recreate discounts and any required subscription workflows.
  4. Trial-import a small sample with several variant types and an older customer record. Inspect rejected rows before importing the full set.
  5. Compare accepted product and variant counts with the source. Check images, stock and prices against actual records, then test a purchase and its confirmation message.

Keep a record of which system accepts new orders during each stage. Assign a staff member to handle pre-move refunds and returns through the original payment route. A migrated order record does not move the original payment transaction.

Shopify’s order export documentation distinguishes captured payment data from authorisation data. Save the relevant payment references and retain authorised access to the original payment provider. Test how staff retrieve an old order before withdrawing their Shopify access.

Redirect products and cut over carefully

Map each old product or collection path to its closest replacement, then implement redirects where the moved domain will be served. If the destination preserves the same paths, test those paths directly. When paths change, use the destination’s supported permanent redirect facility, typically an HTTP 301 redirect.

Shopify’s URL redirect documentation explains its export facility and source-store limitations. A redirect saved only in Shopify will not handle a request that now reaches another host. Import or recreate the mapping on the replacement platform or its hosting layer.

For example, map an old /products/navy-coat path to the replacement coat page, not the home page. Check collection paths and existing redirects too, so an older link reaches its destination without a loop.

Schedule the cutover as an ordered change:

  1. Record the complete existing domain name system (DNS) configuration and the original storefront destination. Retain the email records so a storefront move does not interrupt mail.
  2. Choose a short period for the final transfer. Pause new purchases on the source or capture every order accepted during the transfer window.
  3. Export the final stock and order changes since the trial import. Apply them once, using identifiers that prevent duplicate orders or products.
  4. Change the storefront DNS records to the destination’s required values. Confirm the secure HTTPS connection and the expected shop before reopening purchases.
  5. Complete a purchase from the public domain. Confirm payment, the order record, stock reduction and the customer email.

The stop condition is a failed purchase, an incorrect total or a paid order missing from the destination. Keep purchases closed while you resolve it. If the old shop is still operational, use the recovery procedure below before sending customers back to it.

For a domain bought through Shopify, follow its domain transfer instructions before deactivating the store. The owner starts the transfer. Eligibility and the transfer method depend on the domain extension. Registrar transfer and storefront routing are separate changes, so record both. The destination must support HTTPS.

Keep shopping support working after the move

Reconnect shopping support to the replacement catalogue and policies before it answers customers on the new storefront. Update product identifiers and links, then give order lookups access only to the records the customer is authorised to see.

Use a small set of known records to test the result. The following examples are hypothetical acceptance checks, not measured results.

CheckKnown recordExpected result
Migrated variantNavy coat, medium, SKU COAT-NV-MThe answer and basket use the medium navy variant, not the parent product or another colour
Stock answerThat variant has five sellable units after the final stock importSupport reports availability from the replacement source and links the new product page
Delivery questionThe published policy excludes express delivery to a particular postcodeThe answer preserves that exclusion and does not promise express delivery
Older order enquiryA paid pre-move order remains unfulfilledAuthorised support finds the correct order and status, or passes it to the assigned staff member

Test the older order as its authorised customer and as an unrelated customer. The second customer must not receive the first customer’s details. If historic records remain in a separate system, make the handover route explicit for staff. Keep the customer’s support contact usable through the transition.

Cancel the Shopify subscription last

Cancel only after exports are readable, domain control is secured, checkout works and staff can handle historic orders. Finish app exports first: Shopify uninstalls apps when you cancel the plan.

For an eligible paid store, the store owner follows Shopify’s cancellation procedure:

  1. Open Settings > Plan and select Cancel plan.
  2. Review the options and pending charges. Select Cancel my plan and uninstall all apps, then Continue.
  3. Choose a reason and continue through the remaining prompts.
  4. Enter the owner’s password and select Cancel plan. Retain the confirmation email.

Shopify Plus stores must contact Shopify Plus Support. Eligible stores deactivate at the end of the current billing cycle. Record that endpoint so the team knows when admin access ends.

Under Shopify’s billing guidance, pending charges include app usage, transaction fees and shipping labels. Further charges can arise before closure. Review subscriptions billed directly by third parties, because cancelling Shopify does not settle those contracts. Keep domain renewal active with the provider that will hold the domain.

Pending Shopify Payments payouts continue after deactivation, but resolving payout problems requires admin access through reactivation. Chargebacks can still arrive for past purchases. Save billing and payout records and assign someone to monitor the original payment account.

Recover from an incomplete cutover

Return traffic to the old shop only while it remains available and can safely accept purchases. Restore the saved storefront DNS values if the replacement fails. DNS changes take time to reach customers, so keep both order streams under observation during recovery.

Before reopening the source checkout, reconcile orders and stock accepted by the replacement. A paid destination order must still be fulfilled or refunded, and its stock must not become available for sale twice.

For rejected imports, keep the original exports untouched and isolate the failed rows. Send the destination’s support team the import error and affected identifiers through a secure channel. Correct a copy, rerun a small sample and reconcile the accepted records before retrying the final transfer.

Shopify says store information is guaranteed for two years unless earlier deletion is requested. Reopening requires the owner to select a plan and provide payment details. It cannot restore a store after its data is deleted. Treat that conditional reactivation route as a fallback, while retaining your own records and a working support process.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup