Prepare the configuration.
Create the merchant, locations, staff access, taxes, fulfilment choices, payment connections, and the packages their business needs before importing operational records.
Keep source records traceable
Choose when each channel moves
Keep every exception visible
Accept real workflows before launch
Move in an order the merchant can verify.
Import records carefully.
Map source fields into Box, validate catalogue totals and variants, preserve required source identifiers, and report customer or product records that cannot be accepted.
Test, cut over, and reconcile.
Run representative orders, refunds, bookings, receipts, permissions, and settlement outcomes. Move each channel only after its checks pass and keep every exception visible.
SourceEvery accepted record remains traceable to where it came from.
CohortEach rollout creates evidence and improvements for the next.
AcceptedCompletion means agreed records and real workflows have passed.
Start with what exists.
No two source systems are identical. Before anything moves, establish what the current system contains, what must remain available, and what can be left behind.
Map the records
Identify catalogue items, variants, prices, stock, customers, locations, staff, orders, bookings, invoices, and identifiers used by connected systems.
- Data inventory
- Source identifiers
- Record quality
Map the channels
Record every place the merchant trades today, including websites, counters, payment links, social channels, and back office workflows.
- Customer surfaces
- Payment connections
- Operating workflows
Set acceptance rules
Agree which records must reconcile, who signs off each stage, what can run in parallel, and what would stop a cutover.
- Pass criteria
- Named approvers
- Rollback decisions
Pilot one cohort. Learn before the next.
Choose a representative pilot
Include merchants with different catalogues, locations, channels, and operating patterns so the first cohort tests the range the estate contains.
Turn exceptions into the next playbook
Measure completed trading, reconciled records, outstanding exceptions, support demand, and time to acceptance. Then update mappings, guidance, training, and support routes.
Acceptance is the finish line.
A merchant is migrated when agreed records reconcile, required channels work, real workflows complete successfully, and the institution and merchant accept the result.
See the commerce engine
Everyone knows what they own.
Own the programme
Select merchants, approve data handling, control payment relationships, communicate the move, and decide when each cohort is ready.
Support the deployment
Provide the platform model, configuration path, import interfaces, validation outputs, and technical support agreed for the licence.
Accept the result
Verify the catalogue, staff access, channels, opening position, and first completed workflows before cutover is complete.
Migration questions.
Can every source system be imported automatically?
No. Box first maps the exports or APIs the source makes available. Clean structured records can move directly; incomplete or incompatible records need an agreed correction path.
Does every merchant follow the same plan?
No. The institution can define repeatable cohorts, but each merchant is validated against the channels, data, and packages they actually use.
Can old and new systems run together?
They can where the source system and payment setup allow it. The migration plan defines the overlap, the source of truth during that period, and the reconciliation required before cutover.
What happens to historical records?
The institution decides which history is required for operations, support, reporting, and regulation. Box preserves accepted source identifiers so migrated records can be traced.
When is a merchant considered migrated?
When the agreed records reconcile, required channels work, real workflows complete successfully, and the institution and merchant accept the result.
Start with the estate you have.
Bring the source systems, merchant segments, required records, channels, and rollout constraints. We will turn them into a plan that can be tested before it scales.