Sample deliverable · Synthetic data

A migration plan you can inspect.

A fictional two-product store shows the decisions to resolve before launch. The names, SKUs and paths below are examples, not client records or working Realized routes.

Request a Store Review

Planning example · Not a completed migration

1. Reconcile the catalog and content.

The sample contains two products and three distinct variants. Confirm identifiers, images, inventory and product copy before importing; compare source and destination counts afterward.

Example catalog mapping · 2 products / 3 variants
Source SKU	Product / variant	Target product path	Acceptance check
`FM-CRM`	Field mug Cream / 350 ml	`/products/field-mug`	Confirm variant, image and stock mapping
`FM-SGE`	Field mug Sage / 350 ml	`/products/field-mug`	Keep a distinct SKU for this variant
`BT-500`	Trail bottle Steel / 500 ml	`/products/trail-bottle`	Confirm weight and shipping requirements

Content review covers product descriptions, image alternatives, collection navigation, policies and approved brand assets. Customer and order history require a separate export, privacy and import assessment.

2. Map URLs before changing them.

Start with the actual existing URL inventory, search traffic and backlinks. Assign a relevant destination to each retained page; do not redirect everything to the homepage.

Example URL map · proposed redirects, not live rules
Old path	New path	Action	Acceptance check
`/shop/field-mug`	`/products/field-mug`	301 redirect	Preserve product intent; check both variants
`/shop/trail-bottle`	`/products/trail-bottle`	301 redirect	Confirm the destination returns 200
`/our-story`	`/pages/our-story`	301 redirect	Review content, title and internal links
`/care-guide`	`/pages/care-guide`	301 redirect	Preserve useful support content

After implementation, check the old URL, final destination, canonical tag and internal links. Flag redirect chains, loops and pages without an equivalent destination for a human decision.

3. Agree the acceptance checks.

Shopping and checkout

Test every sample variant, price, availability and cart update.
Confirm payment provider readiness, tax and shipping rules with the owner.
Use the provider’s test mode for successful, declined and canceled payments; do not charge a real customer for QA.
Verify order confirmation and the handoff to fulfillment in an approved test environment.

Mobile and accessibility

Review product, cart and checkout journeys on narrow screens and at 200% zoom.
Use a keyboard to reach navigation, options, forms and errors.
Check labels, image alternatives, visible focus and screen-reader announcements.
Compare page speed and layout stability with the agreed baseline.

Launch and rollback

Name the launch decision-maker and record unresolved issues.
Preserve approved source, content exports and the prior routing configuration.
Agree the change window, final data reconciliation and post-launch checks.
If rollback is needed, preserve new orders and inquiries before restoring traffic.

Training and ownership

Confirm who owns the domain, store, apps, billing and administrator access.
Practice product edits, order handling and the agreed refund process in test mode.
Hand over the mapping, operating notes and outstanding issues.
Agree support scope and escalation contacts without assuming 24/7 coverage.

This sample is a planning structure, not a promise that every migration includes the same work. Paid themes, apps, platform fees, data exports, content production and ongoing support are scoped separately.

Before starting, the written agreement defines deliverables, access, dependencies, fees, acceptance responsibilities and the next decision.

See the Store Review scope Back to Work & Demos