The proposition
One accountable principal,
a named delivery bench
Most merchants replatforming at this size are asked to buy the move and the systems work separately, from two suppliers who each 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 are subcontracted to named partners rather than pretended away.
What is in scope
A migration engagement covers the move itself end to end. The line between this and the next column is drawn at 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 is not comparable 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. The merchant does not hold the subcontract and is never asked to arbitrate between suppliers.
Partners are named in the proposal, before signature — the specific firm, the specific slice, and what they are being paid to do. A merchant doing diligence 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
Stated plainly: no delivery partner is contracted today. The bench is being assembled, and the first engagement's partners will be named to that client at proposal stage rather than presented here as an existing roster. A logo row of firms with no contract behind it is the thing this page exists not to do.
What it costs, and how it is 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 genuinely simple move. Published market rates for Magento to Plus run from around $20,000 to well past $250,000, so this sits at the lower end deliberately — the practice is new and priced accordingly.
Systems integration is quoted on top, per system, once the diagnostic has established what is actually being connected.
Payment is staged against milestones rather than taken up front. The exact split is set in the proposal, because it should follow the shape of the project rather than a standard schedule.
The typical shape
- A deposit at signature
- Instalments at agreed build stages
- A final portion held until after cutover and the post-launch window
Nothing here is a standard schedule — the split follows the project, and it is written into the proposal before signature.
If the principal is unavailable
This is the fair question about a practice with a named principal, and it deserves a real answer rather than reassurance.
The mitigation is structural, not heroic. Everything that matters lives where the client can reach it: the store is built in the merchant's own Shopify account, the code in a repository they own, the runbook and URL map as documents in their possession from the day they are written. There is no stage of the project where the work exists only on one person's machine or only in one person's head.
For the cutover specifically — the window where unavailability would hurt most — the runbook is written to be executable by a competent third party, and the subcontracted partners on the engagement are already inside it. A merchant who wanted to complete the move with someone else could hand over the repository, the runbook and the access list and be understood in an afternoon.
That is the honest version. It does not claim a bench that would absorb the loss without noticing; it claims that nothing is hostage.
Tell us what is breaking
What the systems are doing now, and what you need them to do. We will tell you whether it is a platform problem or something cheaper.