Inventory data and dependencies
Rehearse import and reconcile
Approve cutover and monitor

Identify what the old store actually contains

Begin with an inventory of the source platform, catalog, customer records, historical orders, content, media and active connections. Add the less visible items: discount rules, subscription arrangements, store credits, delivery restrictions and notifications. Each may need a different migration method or a deliberate decision to leave it behind. The discovery record should distinguish required continuity from optional redesign ideas.

Do not assume that an export file is a complete backup or that every record type has an equivalent destination. Open sample exports and inspect their fields. Confirm whether product images remain accessible, whether variants retain their identifiers and whether records reference other records. The work estimate should be based on these samples rather than only the total number of products.

Assign an owner to each data set. A developer can identify an inconsistent weight field, but the merchant must confirm the correct value. Finance and operations may need access to the previous system for reasons unrelated to the new storefront. Decide how records will be retained before closing accounts or removing subscriptions.

Use a rehearsal to expose import problems

Shopify supports different migration methods for different data types, including manual transfer, CSV imports, applications and custom solutions. Its migration guide specifies importing products, then customers, then historical orders so relationships can be established. The exact approach still depends on the source system and the information available.

A rehearsal should use a representative selection of records before the full transfer. Include products with several options, unavailable stock, unusually long descriptions and more than one image. Compare the imported result against the approved source, including prices, weights, variant combinations and visibility. A record count alone cannot show whether the data is usable.

Keep a reconciliation log of accepted records, rejected records and transformations. For instance, two differently formatted category labels may be deliberately combined, while duplicate product identifiers require investigation. Record the decision and its approver. Repeating a corrected import should have a predictable effect; the team needs to know whether it updates existing records or creates duplicates.

Plan the customer experience across the change

Customer data and customer access are separate migration questions. Shopify's checklist explains that encrypted passwords do not transfer with customer records. The chosen account experience therefore needs a communication and support plan. Avoid promising that everyone will sign in exactly as before until the source and destination account flows have been verified.

Consider what a returning buyer will ask on the first day: where to find an earlier order, how to use an outstanding credit and whether a recurring purchase continues. These questions should have approved answers before launch. Subscription or loyalty applications may require their own migration arrangements; their presence in the old store does not establish compatibility with a new application.

Messages about the move should explain only what customers need to do. A clear account-access instruction is more useful than a long announcement about the platform. The merchant approves recipients and communications, and existing marketing preferences should not be silently broadened during data cleanup. Support staff need the same explanation customers receive.

Preserve useful paths into the catalog

Build an old-to-new URL map before the domain changes. Include important product and collection pages, editorial content and policy pages. Use available search, analytics and backlink information to identify valuable entry points, while also checking links used in customer emails and printed materials. The map should describe the intended destination for each retained page.

Shopify provides URL redirects, but their behavior and restrictions need checking against the actual paths. A redirect is useful when it takes a visitor to a relevant replacement. Sending every retired product to the homepage may leave buyers confused. Where there is no equivalent item, decide whether a category, explanatory page or normal unavailable-page response best matches the situation.

Google describes site moves as a process that requires discovery and reprocessing of changed URLs. Search visibility can fluctuate. No migration plan can guarantee unchanged rankings. Preserve useful content and internal links, verify redirects, and monitor indexing after launch rather than treating the domain switch as the end of SEO work.

Control the final changes before switching stores

The rehearsal is a snapshot; the live business may continue taking orders afterward. Define a final data cutoff and identify which changes must be brought across before launch. Inventory, new customers and new orders can each have different sources of truth. The plan should state who stops edits, who performs the final transfer and how discrepancies are resolved.

Document the domain change separately from email service. A website move should not casually overwrite records that support business email or other services. The authorized person making the change needs the current configuration, the intended changes and a recovery path. Keep the old platform available for the agreed transition period instead of cancelling it as soon as the new homepage loads.

A launch decision should require evidence from the new store: representative orders, correct delivery options, customer-facing messages and access for the people operating it. Shopify's test-order documentation describes supported ways to test payment and order settings. Test mode prevents live purchasing while active, so the launch check must explicitly confirm the intended payment state.

Agree on the migration deliverables and limits

A migration proposal should name the source platform, record types, import method, cleanup allowance, URL mapping and verification work. It should also identify theme implementation, copy changes and custom integrations as included or separate. Moving a clean catalog into an established design is a different scope from rebuilding the store and replacing several operational systems at once.

Pricing depends on the quality and complexity of the source data, not simply the word migration. Dappr needs sample exports, access requirements and a list of business-critical connections to provide a meaningful scope. Third-party migration tools, Shopify subscriptions and other recurring fees should be listed separately from project labor.

The handoff should include the reconciliation record, unresolved exceptions and the responsibilities for post-launch monitoring. Review orders, broken paths and customer support issues during the agreed follow-up period. If a problem appears, the record of what moved and when gives the team a place to investigate instead of guessing whether it originated in the old data or the new configuration.

Questions before you begin

Will customer passwords move to Shopify?

Shopify's migration checklist says encrypted passwords do not transfer with customer records. The account-access plan must reflect the chosen Shopify account experience and include clear instructions where customer action is needed. Test it before telling returning customers what to expect.

Can every historical order be migrated?

That depends on the source data, available export and selected import method. Inspect the required fields and relationships before promising complete transfer. Some records may need archival access in the old system, with the merchant deciding retention requirements.

Can the old store keep selling during preparation?

Often the new store can be prepared while the old one remains active, but a final reconciliation is still required. Agree on a cutoff for changes and a method for handling new orders, customers and inventory. The plan must prevent two stores from becoming conflicting sources of truth.

Does migration guarantee that search traffic stays the same?

No. Search engines need to process the changed site, and rankings can fluctuate. Relevant URL mappings, preserved content, working internal links and monitoring reduce avoidable problems, but they do not guarantee a particular traffic result.

What makes a migration more expensive?

Inconsistent product data, complex variants, custom applications, historical records and multiple sales connections add investigation and testing. A redesign or extensive content rewrite also adds scope. Sample exports and a dependency inventory help separate necessary migration work from optional improvements.

Shopify migration with a plan for every important record