| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 1271 |
| Technical Name |
flexigo_migration_base |
| License | LGPL-3 |
| Website | https://flexigotech.com |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 1271 |
| Technical Name |
flexigo_migration_base |
| License | LGPL-3 |
| Website | https://flexigotech.com |
| Versions | 17.0 18.0 19.0 |
Migration Base for Odoo 19
Shared technical governance for ERP migration toolkits—control project lifecycle, reconcile data, and maintain audit trails across accounting transfers.
The challenge with ERP migrations
Accounting and ERP migrations—whether from QuickBooks, NetSuite, Sage, or Xero—leave companies vulnerable. Raw staging data lingers without validation records, trial balances sit un-reconciled, audit trails disappear, and GDPR erasure rights go untracked. Each migration connector built independently means repeated models, inconsistent security, and weaker compliance posture. The cost of failure: audit findings, regulatory fines, and loss of rollback evidence.
Migration Base solves it natively
Migration Base provides the shared technical and governance layer all migration connectors inherit. It manages project lifecycle states, holds staging records with full lineage, enforces versioned field/value mappings, tracks reconciliation sign-offs, archives migrated data with PII markers for GDPR compliance, and logs every run for audit and rollback analysis. Multi-company isolation and role-based access control are built in. Dependent connectors (QuickBooks, NetSuite, CSV) extend this base instead of reimplementing it, ensuring consistency and reducing deployment risk.
Key capabilities
Governed Project Lifecycle
Move projects through defined states: draft → connected → extracted → mapped → validated → loaded → reconciled → live. Prevent skipped steps; block go-live until the go/no-go checklist is complete.
Staging & Lineage
Store raw source payloads in staging records with source ID, realm, and run reference. Every record migrated carries lineage metadata—who pulled it, when, and which mapping version was used.
Reconciliation & Audit
Record trial balance, AR/AP ageing, and inventory variance sign-offs. Immutable run logs and historical archives with PII erasure markers support audit discovery and GDPR compliance.
Versioned Mappings
Define field/value/dimension mappings once, version them, and reuse across runs. Support multi-source migrations without data duplication.
Multi-Company Isolation
Every migration project, staging record, mapping, run, and archive is company-scoped. No cross-tenant visibility; manager-only write access controls.
GDPR & Compliance
No secret storage; explicit retention basis for archived records; PII erasure support for GDPR Article 17. Audit trail of who accessed what and when.
Watch the 2-minute walkthrough
English — 2-minute walkthrough
Español — walkthrough de 2 minutos
Deutsch — 2-Minuten-Rundgang
See it inside Odoo
Who it is for
- Migration Managers — manage project lifecycle and sign-offs
- Accounting teams — reconcile and validate data transfer
- Compliance & audit — track lineage and enforce controls
- System integrators — extend base for their connectors
- Finance controllers — review reconciliation before go-live
Compatibility
Odoo 19 Community and Enterprise. No external SaaS required. Designed to be extended by migration connector modules (QuickBooks, NetSuite, Sage, Xero, CSV). Depends on base, mail, and account modules.
Licensed: LGPL-3 (free public). Dependent connectors may be premium.
Pricing decision: FREE
Open-source base for the migration ecosystem. Dependent paid connectors extend this foundation.
€0
Licensed LGPL-3
Frequently asked questions
What is a "base module" and why do I need it?
Migration Base is the shared foundation that all migration connectors (QuickBooks, NetSuite, Sage, etc.) inherit from. Instead of each connector reimplementing the same models, security, and audit trails, they all extend this base. This ensures consistency, reduces bugs, and makes compliance easier. You install Migration Base once, then add whichever connector(s) match your source system.
Does this module actually migrate my data, or just manage the process?
Migration Base manages the process and holds the data in staging records, but does not pull data from your source system itself. That job belongs to a connector module (e.g. flexigo_quickbooks_to_odoo). Migration Base stores the payloads, validates them, tracks the mapping, logs the run, and supports audit and rollback. Connectors use this base to do the actual extract & load.
Is it GDPR-compliant out of the box?
Yes. Migration Base supports explicit retention basis for archived records, PII erasure (Article 17), data minimisation, and full audit trails (Article 30). You document the lawful basis in the project record, and the module tracks who accessed what data and when. This satisfies the technical measures required by GDPR Article 32.
Can I use this for multi-company or multi-source migrations?
Yes. Every migration project, staging record, and archive is company-scoped. You can run separate projects for each target company or source system. Versioned mapping sets let you reuse transformations across multiple runs without duplication.
What happens to my staging data after go-live?
After reconciliation and go-live approval, you archive the run. The archive is immutable, compressed, and marked with a retention basis (e.g. "7 years for audit"). You can then erase PII from the staging records if they are no longer needed. The archive preserves the evidence for audits, and you define when to permanently delete it.
Ready to govern your migration?
Install Migration Base and choose the connector that matches your source system (QuickBooks, NetSuite, Sage, or CSV).
Learn more at flexigotech.com
Please log in to comment on this module