Your parties, ports, charges and mail history brought across with tooling that reads first, reports what it found, and touches nothing without a dry run.
The market treats migration as weeks of paid consulting and a leap of faith on data quality. Bad legacy data does not disappear in the copy — it becomes bad live data with an invoice attached.
Read-only checks over parties, ports, links and lanes — SELECTs only, never writes. The report is the first deliverable.
Near-duplicate parties surface as merge groups with reference counts and a suggested survivor. Deciding stays human.
Repairs print their plan and refuse to write without an explicit flag. Faith is not a migration strategy.
Mail backfill brings the correspondence, not just the master data — the story of each shipment comes along.
Data migration
Old records cross over audited and dry-run first; nobody re-keys a moving shipment.
| The moment | The typical vendor migration | Naulon |
|---|---|---|
| The timeline | Four to eight weeks of implementation, quoted after the demo. | A published 30-day plan you can read before you talk to anyone. |
| The approach | A big-bang cutover everyone dreads. | Both systems for a month; the old one empties by attrition. Nobody re-keys a moving shipment. |
| Data quality | Imported as found, discovered as problems later. | A read-only audit runs FIRST and reports what it found — before anything is written. |
| Duplicates | Copied in, deduplicated by hand for months. | Merge groups detected with a suggested survivor and reference counts — you decide, the tool counts. |
| Writes | Scripts run against your data on faith. | Every repair defaults to dry-run; writing requires an explicit flag. The plan prints before anything changes. |
| Mail history | Usually left behind. | The mailbox backfill re-reads history into the same pipeline live mail uses — proven to re-read without refetching. |
| The safety net | "We take backups." | Backups proven restorable by an actual restore drill, not by the word "verified" in a report. |
