Move to Datrylo with a clear plan
A migration is more than copying rows from one system into another. It is a chance to decide which records remain useful, how they map to a new workflow and what the team must be able to reconcile before it trusts the result.
Choose the source and agree the retained history
Plan your move to Datrylo with clear data mapping, opening balances and historical records.
| Source / decision | Target treatment and accountable review |
|---|---|
| Source inventory | Customer fileSRC-C01,productSRC-P01,open invoiceSRC-I01 and stock by location;record source system/version,date and export owner. |
| Mapping / decision | Map customer identity,product units and outstanding amounts separately;choose detailed open documents or reviewed opening balances with finance approval. |
| 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 | Historic closed transactions,reports,attachments and source licences remain in the agreed accessible archive unless detailed conversion is explicitly accepted. |
| 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.
Define what needs to move
List the systems, business entities, locations and applications in scope. Separate reference data such as customers and products from open transactions, balances, stock and historical documents. Decide which history must remain in the old system for read-only access and which must be available in Datrylo. The answer depends on your reporting, legal retention and operational needs.
Clean and map a small sample
Choose representative records, including duplicates, missing fields and unusual cases. Map them to the agreed Datrylo structure and document any transformation. Do not hide rejected rows; give each a clear owner and resolution. For stock, compare quantities and locations. For finance, reconcile opening balances and posted documents with the responsible finance team.
Rehearse the complete workflow
Import a sample into an isolated, neutralized environment. Run the first day of work: find a customer, create an order, receive or deliver goods, post the required document and produce the report people use. Test roles, language display and downstream integrations. A fresh test Workspace can support the rehearsal, but the business data and any source-specific conversion still need validation.
Agree the cutover and recovery path
Identify when source data becomes read-only, how late changes are captured and how reconciliation will be signed off. Keep a verified source backup and a safe rollback decision point. Avoid sending test emails or live payment events from migrated copies. Record who decides to proceed and who handles issues after launch.
Ask the right first question
Tell us your current system, approximate record volumes, required history, target workflows and deadlines. We can then scope an assessment without promising an automatic one-click move or a fixed duration before the data is inspected. Discuss migration.