The proposition
One accountable principal,
a named delivery bench
Buy the move and the systems work from two suppliers, and each can blame the other when the cutover slips.
Crossdock takes the whole thing as prime contractor: the platform move, the integrations behind it, and the cutover. Specialist slices go to partners who are named to you before anything is signed.
What's in scope
A migration engagement covers the move itself end to end. The line between the two columns below is drawn in the proposal, in writing, before anything starts.
Standard
- Discovery, and the technical audit of the existing store
- Theme build or port, checkout, and the storefront itself
- Product, customer and order data migration, with reconciliation
- The URL map, redirects and the search-continuity work
- Payments, tax and shipping configuration
- The cutover runbook, the cutover itself, and the rollback plan
- Thirty days of post-launch support
Priced separately
- ERP, WMS or OMS integration — scoped per system, because the effort varies widely between them
- Rebuilt custom logic that has no native or app equivalent
- Content writing and photography
- Ongoing retained support beyond the first thirty days
- Paid search, feeds and channel setup
Nothing moves between those columns after the proposal is signed without a written change and a revised number. A migration that quietly grows in scope is how both parties end up unhappy.
Who does the work, and who carries it
Crossdock contracts as prime. One agreement, one invoice, one party accountable for the outcome — including for work performed by a subcontractor. You don't hold the subcontract, and you're never asked to arbitrate between suppliers.
Partners are named in the proposal, before signature — the specific firm, the specific slice, and what they're being paid to do. You can look them up before committing.
Delivered directly
- The storefront
- The migration itself
- Redirects and search continuity
- The cutover
Subcontracted to a specialist
- ERP and warehouse-system integration
- Unusual payment or tax work
- Heavy data engineering on very large catalogues
What it costs, and how it's paid
The working band for a migration delivered as prime contractor is £15,000 to £25,000, with £10,000 as a floor for a simple move.
Systems integration is quoted on top, per system, once the systems review has established what's being connected.
Payment is staged across three milestones: project start, interim review and go-live.
Three milestones
- Project start, when the scope is agreed and the engagement signed
- Interim review, when you review the new store as a preview in your own account
- Go-live, once the cutover has run and the store is taking orders
Each payment falls due when something you can check has happened. The split follows the project and is written into the proposal before signature.
If the principal is unavailable
The safeguard is structural. Everything that matters lives where you can reach it: the store is built in your own Shopify account, the code in a repository you own, the runbook and URL map as documents you hold from the day they're written. At no stage does the work exist only on one person's machine or in one person's head.
For the cutover, where unavailability would hurt most, the runbook is written so a competent third party could run it, and the subcontracted partners on the engagement are already inside it. If you wanted to complete the move with someone else, you could hand over the repository, the runbook and the access list and be understood in an afternoon.
Nothing about the project is hostage to one person.
Tell us what you need
What the systems are doing now, and what you need them to do. We'll tell you whether it's a platform problem or something cheaper.