Inventory data and dependencies
Review up to 500 products, 2,000 customer/order records and required integrations.
Identify supported fields, record counts and portability questions before the transfer.
Map your catalogue, important URLs, integrations and responsibilities before switching your store to Shopify.
Prices cover the listed scope. Additional work and external costs are quoted separately.
We agree a data map and test a representative sample before the final transfer. Every unresolved item has an owner and a decision before launch.
| Area | Map before transfer | Check in Shopify |
|---|---|---|
| Products & variants | Identifiers, options, prices, media and inventory. | Compare counts and inspect complex product examples. |
| Customers & sign-in | Contact fields, permissions and the new account route. | Validate sample records and customer access; passwords do not transfer. |
| Historical orders | Supported fields, order references and import method. | Reconcile totals and document unavailable history. |
| Important URLs | Priority source pages and their destination URLs. | Test the agreed redirects and flag unsupported paths. |
| Apps & operations | Payments, shipping and connected systems. | Run the agreed shopping and fulfilment scenarios. |
| Launch handover | Final data changes, domain switch and rollback decision. | Record sign-off, remaining issues and monitoring ownership. |
The test import exposes missing fields and unexpected behaviour before the store switches platforms. Any data cleanup, redesign or unsupported integration is scoped from those findings.
Plan and rehearse a Shopify migration with defined record limits, feature exceptions and priority URL mapping.
Review up to 500 products, 2,000 customer/order records and required integrations.
Identify supported fields, record counts and portability questions before the transfer.
Map supported fields and complete one test import.
Reconcile counts and inspect representative products, customers and order records.
Prepare up to 200 priority URL mappings and check the destination buying flow.
Validate agreed redirects and document feature or account-access exceptions.
Agree the final sync, launch owner, rollback point and fourteen-day post-launch checks.
Record the go/no-go decision and resolve or accept outstanding launch issues.
Data mapping and reconciliation, feature exception matrix, redirect register and cutover/rollback checklist.
Outside this scope: Password portability promises, unsupported subscriptions/history, custom ERP, paid apps and a redesign
4–6 weeks after discovery
New theme design and transfer-tool fees separate
Counts are planning limits; final feasibility fixes the scope before price confirmation
If the full scope is beyond your budget, we’ll prioritise the most useful work and agree a smaller first phase with you.
Share what is available. We’ll identify any missing access or inputs during scoping.
Published prices apply to the listed scope. Deliverables, timing, revisions and external costs are confirmed before work starts.
An illustrative delivery approach to help you review the scope. This is a planning example, not a client case study.
| Stage | Example work | Acceptance or decision |
|---|---|---|
| Products and media | Map identifiers, variants, images, collections and inventory fields. | Reconcile counts and inspect representative complex products. |
| Customers and orders | Map supported fields; document sign-in, historical-order and subscription exceptions. | Test records and customer access without assuming transferable credentials. |
| URLs and launch | Map priority URLs; rehearse final sync, redirects and rollback. | Name the go/no-go owner and record the accepted interruption window. |
Illustrative platform screens show the type of work and reporting. These are not client results.
Reconcile catalogue entities and review import exceptions before cutover.
Map source URLs to their destinations and record the redirect acceptance status.
Organise product titles, stock, publication status and catalogue structure.
Separate indexed pages from redirects, exclusions and URLs that need investigation.
Explore eight illustrative projects, from the initial brief to delivery and acceptance. Businesses and data in these walkthroughs are fictional.
Moving a homewares catalogue from WooCommerce to Shopify.
Illustrative project
Explore the walkthroughAn agreed theme, layouts and catalogue.
Custom sections or a separately scoped theme.
Data migration and feature replacement.
Migration starts with an agreed data inventory, test import and exception list. Products, customers, historical orders and URLs need separate mapping and validation; not every source feature or credential transfers directly. The starting limits are listed below. Agree the final sync, launch window, rollback conditions and owner before changing the live store.
Treat them as separate feasibility questions. Customer sign-in may require an account activation or reset path depending on the systems. Subscription continuity depends on providers and permissions. Historical order fields must be tested; do not assume every source field or payment credential can be copied.
A cutover plan should state any order/content freeze, expected interruption, final sync and rollback point. The actual window depends on the source, integrations and rehearsal results, so it must be agreed after discovery.
$2,500 – $6,000 / standard migration. New theme design and transfer-tool fees separate These are published USD prices. The written quote must state the complete cost, payment schedule and applicable taxes.
4–6 weeks after discovery. To scope the work, prepare: Source platform; record volumes; essential apps/features. The schedule starts after the required access, inputs and approvals are ready.
Use the listed deliverables and exclusions as the starting point. The quote must state acceptance checks, review rounds, payment stages, cancellation arrangements and any ongoing support. Requested additions need an agreed cost and schedule before implementation.
Tell us where you are, what needs to change, and what success would look like for your business.