Move from a legacy ERP to Datrylo
A legacy ERP may hold the only record of transactions, approvals or reports a business still depends on. A migration should begin by identifying those obligations before choosing a technical export method. Map your records, reconcile opening balances and rehearse the first working day before moving to Datrylo. The migration scope depends on your source system and customisations.
Inventory the source version and undocumented dependencies
Plan your move to Datrylo with clear data mapping, opening balances and historical records.
| Source / decision | Target treatment and accountable review |
|---|---|
| Legacy customer / stock | SampleLEG-C01 andLEG-P01 map to contact/product with signed unit and location meaning. Data owner confirms export permissions and source version. |
| Undocumented process | One report calculates credit exposure outside the ledger. Finance documents its formula and source before selecting a target report or custom replacement. |
| Trial / reconciliation | Illustrative trial:2 source customers →2 targets;opening receivables100,000 →90,000 leaves10,000 unresolved. Finance owner traces the missing reference before acceptance. |
| History / boundary | Preserve accessible historical reports and documents;unknown schema,unsupported exports and missing licences remain blockers until reviewed,not assumed migration support. |
| Cutover / decision owner | Business owner holds cutover while10,000 is unresolved. Data owner dates the final export; finance signs balances; operations signs quantities. Agree transaction freeze,source-of-truth and reversal decisions before switching. |
Use this worksheet to organise your requirements, assign owners and plan the next steps.
Decide what must survive
List master data, open transactions, balances, stock, documents, audit history and reports. Distinguish data needed for daily work from history that can remain in a protected read-only archive. Ask the finance and operations owners to sign off on the cutoff and reconciliation rules.
Build a source-to-target map
Document fields, IDs, units, currencies, statuses and relationships. Export a small but difficult sample, including a cancelled order, partial delivery and corrected invoice. Load it into a neutralized Datrylo environment and check both record meaning and workflow behavior. A row count alone is not a migration test.
Rehearse cutover
Time the export, transformation, import, reconciliation and user checks. Decide when the source becomes read-only and how late transactions will be captured. Retain verified source backups and a rollback route. External integrations should be disabled in the test copy. Discuss your legacy system.
Explore the connected workflow
Let's build your next way of working
Tell us what your business needs. Whether you are choosing applications, planning a move or looking for a custom solution, the Datrylo team can help you take the next step.