Move from Odoo Community to Datrylo
Datrylo builds on Odoo Community, but a migration still needs technical and business verification. The source may have a different release, hosting setup, module versions, custom add-ons or database policies. Datrylo uses a shared Cluster release and gives each Workspace database its own subscription. A source database is not automatically safe to import into that service.
A shared foundation does not make databases interchangeable
Plan your move to Datrylo with clear data mapping, opening balances and historical records.
| Source / decision | Target treatment and accountable review |
|---|---|
| Source version / add-ons | Inventory installed source modules,custom models and version. Map partner/product external references and agreed units before deciding data conversion. |
| Open transaction / access | Source order OC-10 has10 ordered/6 delivered/4 due;test all three quantities and ordinary-role access after mapping. Do not assume source record rules survive conversion. |
| 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 | Retain source custom code provenance,licences,reports and documents;version conversion and add-on compatibility require a separately tested scope,not a direct database swap. |
| 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.
Inspect the source installation
List the Odoo version, installed modules, licences, custom code and external connections. Identify which data and attachments must move and which scheduled jobs or webhooks must be neutralized in a test Workspace. Compare the source module closure with the exact Datrylo Cluster release and approved application package. Odoo's export/import guide describes standard data movement, but complex upgrades require a separate migration plan.
Test business continuity
Move a representative sample: contacts, products, open sales, stock and invoices if in scope. Reconcile record counts and financial/stock totals. Run one normal and one exception workflow with real user roles. Preserve historical identifiers or an explicit cross-reference so people can find old documents.
Protect the source
Take a verified backup and define a cutover point. Keep the original system available under an agreed read-only policy until reconciliation passes. Neutralize outbound mail, payments and other live actions in duplicates. Discuss your Community migration path.
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.