Migrate in phases. Start with an inventory of what you use, then move master data, open balances, and active rates, and rebuild your integrations and third-party connections. Run the new system alongside CargoWise one branch or mode at a time until your team is confident, archive the history you're required to keep, and only then switch the old system off.
Why migrate in phases
Forwarders are rightly wary of ripping out a system that runs every shipment, invoice and customs filing. A phased move limits the blast radius: if something goes wrong, it affects one branch or one mode while everything else keeps running on the system it knows. It's the approach DSV is taking at global scale, moving operations to a new system region by region (Container Magazine).
Eight steps to migrate
- Inventory what you use. Modules, workflows, reports, integrations, automations, and the workarounds outside the system. Many forwarders use a fraction of what they pay for.
- Confirm the target. Whether it's a custom system or another product, design it around the inventory rather than the old system's screens.
- Plan for history. Decide what migrates and what goes to a searchable archive, based on the retention rules in each country.
- Migrate the foundations. Organizations, contacts, addresses, charge codes, chart of accounts, open AR and AP balances, and active rates. Clean them on the way. Migrating master data with errors carries the errors into the new system.
- Move integrations and third-party systems. Carrier connections, EDI partners, customs interfaces, accounting, customer portals, and any apps your teams rely on.
- Run in parallel. Start with one branch, mode, or customer group. Run real jobs in the new system with the old one as reference, and compare results.
- Expand. Add branches and modes as each one proves itself, with training on the agreed processes before each go-live.
- Switch off. Only when the last group is live, the archive has been validated, and contract notice periods are handled.
What to migrate and what to archive
| Data | Usual approach |
|---|---|
| Organizations, contacts, addresses | Migrate, cleaned and de-duplicated |
| Charge codes and chart of accounts | Migrate, often redesigned first |
| Active rates and contracts | Migrate |
| Open jobs | Finish in the old system or migrate at cut-over, by mode |
| Open AR and AP balances | Migrate as opening balances, reconciled |
| Closed jobs, entries, and documents | Searchable archive, or migrate recent years only |
| Audit trail | Archive with the records it supports |
Risks and how to manage them
| Risk | How to manage it |
|---|---|
| Incomplete data export | Test exports on a sample period early, before notice is given |
| Integration gaps on go-live | Rebuild and test every connection in the new system before parallel running starts |
| Teams reverting to old habits | Agree standard procedures and train on them before each go-live |
| Finance surprises at month-end | Align charge codes and the chart of accounts first, and run a full month-end in parallel |
| Losing audit access to history | Validate the archive by retrieving records the way an auditor would |
Before you give notice
- Read your agreement for notice periods, minimum terms, and data export terms.
- Run a test export and check it against the source.
- Have the archive approach agreed with your broker or counsel.
- Know which branch or mode goes first.
Common questions
How long does a migration take?
It depends on the number of branches, modes, countries, and integrations. Each phase has an agreed timeline, and the first group goes live before the rest are scheduled, so you see progress early.
Do we have to migrate all our history?
No. Most forwarders migrate recent and open work and move older history to a searchable archive that meets their retention obligations.
Can we move to a new system and keep some CargoWise functions?
Yes. Some forwarders keep CargoWise for specific countries or modes during or after the move, with the two systems connected through integrations.
Who moves our integrations?
We do. Integrations, third-party systems, and software your teams rely on are part of the migration plan, rebuilt and tested before parallel running starts.