ERP migration
Field-level mapping, validation, and rollback between Freedom ERP and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
Freedom ERP
Source
Dolibarr ERP
Destination
Compatibility
9 of 12
objects map 1:1 between Freedom ERP and Dolibarr ERP.
Complexity
BStandard
Timeline
4-8 weeks
Overview
Moving from Freedom ERP to Dolibarr is a database-first migration: Freedom ERP has no documented REST or SOAP API, so we extract data directly from the underlying database (SQL Server or equivalent) or through module-level CSV exports. We map each Freedom ERP module to the corresponding Dolibarr module or Dolistore extension, resolving BOM complexity (multi-level component trees with scrap rates) against Dolibarr's product variant model, and flagging that Dolibarr has no native production planning or quality control module—these require a Dolistore extension or manual reconstruction using Projects. Open AP/AR, GST registration details, employee records, and payroll summaries migrate into Dolibarr's accounting and HR modules. We do not migrate Freedom ERP workflows, custom alerts, or custom screens as code; we deliver a written inventory for the customer's admin to rebuild in Dolibarr's native configuration tools.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Freedom ERP object lands in Dolibarr ERP, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Freedom ERP
Customer
Dolibarr ERP
ThirdParty (type = Customer)
1:1Freedom ERP Customer records map to Dolibarr ThirdParty with the Client checkbox enabled. GST registration number, state code, and billing address transfer to ThirdParty extrafields or address fields. We resolve the customer dedupe key (GSTIN or email) before insert and create the ThirdParty record before any related Order or Invoice import so that the foreign key reference is satisfied at migration time.
Freedom ERP
Vendor
Dolibarr ERP
ThirdParty (type = Supplier)
1:1Freedom ERP Vendor records map to Dolibarr ThirdParty with the Supplier checkbox enabled. PAN, GSTIN, and payment terms transfer to extrafields. Vendor-linked GRN records and open PO history migrate as Supplier Order and Bill records after the ThirdParty insert is validated. Payment terms (such as Net-30 or Net-45) map to Dolibarr's cond_reglement_code field.
Freedom ERP
Item
Dolibarr ERP
Product
1:1Freedom ERP Items (raw materials, intermediates, finished goods) map to Dolibarr Product records. Item type (stockable, service, assembly) maps to Dolibarr's psm type field. Unit of measure, standard cost, and warehouse assignment transfer directly. Stock quantities from the stores module migrate to Dolibarr's stock_warehouse_product table. Item codes become Product refs and are used as the dedupe key during import.
Freedom ERP
Bill of Materials
Dolibarr ERP
Product (variant model)
lossyFreedom ERP BOMs define multi-level product structures with component quantities, scrap rates, and phantom assemblies. Dolibarr has no native multi-level BOM engine; we decompose the BOM tree and represent each level as a Dolibarr Product with the is_assembly variant type, linking child components through the BOM module from Dolistore or using product kit associations. We preserve scrap percentages and multi-level routing as extrafields on each assembly variant. This step requires a planning day to reconstruct the full BOM tree before migration begins.
Freedom ERP
Chart of Accounts
Dolibarr ERP
Accounting (manual chart setup)
1:1Freedom ERP Chart of Accounts (account type, group, cost-center, and GST/S-tax mapping) exports directly from the accounts table. Dolibarr's accounting module requires manual chart of accounts setup—typically by importing the relevant country's standard chart (India GST-compatible charts are available from the Dolibarr community). We export the Freedom ERP account structure and provide a mapping template so the customer's accountant can configure the Dolibarr chart with account codes, names, and type groupings intact.
Freedom ERP
Open AP/AR
Dolibarr ERP
Invoice / SupplierInvoice
1:1Outstanding Freedom ERP receivables and payables map to Dolibarr Facture (Customer Invoice) and FactureFournisseur (Supplier Invoice). Invoice status (unpaid, partially paid) maps to Dolibarr's fk_statut. GST amounts separate into TVA extrafields for Indian compliance. Open invoice aging and due dates migrate as Payment schedule lines. We export by fiscal year to avoid triggering Freedom ERP performance degradation during the export phase.
Freedom ERP
Production Order
Dolibarr ERP
Project or MRP Module (Dolistore)
lossyFreedom ERP Production Orders link BOMs, work centers, scheduling dates, and output quantities. Dolibarr has no native production planning module; the customer must select and install an MRP extension from Dolistore (such as MRP Pro or Manufacturing) before production order import, or the orders migrate as Dolibarr Projects with structured task lines and custom fields for routing and output. We configure this during the Dolibarr setup phase and advise the customer on extension selection before migration begins.
Freedom ERP
Quality Control Records
Dolibarr ERP
Project (task-based) or Extrafields on Product
lossyFreedom ERP QC inspection records link to production lots and item batches with inspection criteria, results, and defect logs. Dolibarr has no native QC module. We import inspection records as Dolibarr Projects with structured tasks capturing inspection type, lot reference, result (Pass/Fail), and defect descriptions in extrafields. The customer may alternatively install a Dolistore QC module if available for their Dolibarr version.
Freedom ERP
Maintenance Records
Dolibarr ERP
Asset (with intervention tracking)
1:1Freedom ERP equipment and machine maintenance logs (work orders, spare parts consumed, technician assignments) map to Dolibarr Asset records with intervention notes in extrafields or Project-linked tasks. We export maintenance history, equipment master data, and linked spare part consumption records. Post-migration, the customer can enable Dolibarr's asset tracking and create intervention logs as Asset-linked tasks.
Freedom ERP
Employee
Dolibarr ERP
HR Module (User)
1:1Freedom ERP Employee records (personal details, department, designation, date of joining, status) map to Dolibarr User records when the HR module is activated. We preserve org hierarchy through Dolibarr's hierarchical user reporting structure. Salary components and payrun history migrate as earning and deduction summaries mapped to custom extrafields on the User object. Actual payroll processing configuration in Dolibarr HR is scoped separately from the migration.
Freedom ERP
Payroll Records
Dolibarr ERP
HR Module (custom extrafields on User)
1:1Freedom ERP payroll data includes salary components, statutory deductions (PF, ESI, TDS), and payrun history. We export payrun summaries and individual earning records as structured CSV. These map to Dolibarr User extrafields for salary and deduction tracking. Actual salary run configuration, bank payment file generation, and statutory compliance setup in Dolibarr HR are outside standard migration scope and are recommended as a separate configuration engagement.
Freedom ERP
Gate Entry Logs
Dolibarr ERP
Stock Movement (Inventory module)
1:1Freedom ERP gate entry records track inward and outward material movement with vehicle details, challan references, and material descriptions. We export gate entry logs as structured records and map them to Dolibarr Stock Movement entries (mouvement_stock table) linked to the relevant Product and warehouse. Material inward maps as stock entry; outward maps as stock exit. The customer validates the warehouse assignment before the import batch runs.
| Freedom ERP | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Customer | ThirdParty (type = Customer)1:1 | Fully supported | |
| Vendor | ThirdParty (type = Supplier)1:1 | Fully supported | |
| Item | Product1:1 | Fully supported | |
| Bill of Materials | Product (variant model)lossy | Mapping required | |
| Chart of Accounts | Accounting (manual chart setup)1:1 | Fully supported | |
| Open AP/AR | Invoice / SupplierInvoice1:1 | Mapping required | |
| Production Order | Project or MRP Module (Dolistore)lossy | Fully supported | |
| Quality Control Records | Project (task-based) or Extrafields on Productlossy | Mapping required | |
| Maintenance Records | Asset (with intervention tracking)1:1 | Mapping required | |
| Employee | HR Module (User)1:1 | Fully supported | |
| Payroll Records | HR Module (custom extrafields on User)1:1 | Mapping required | |
| Gate Entry Logs | Stock Movement (Inventory module)1:1 | Mapping required |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Freedom ERP gotchas
No public API requires direct database migration path
Custom fields stored outside standard tables
Large data volumes trigger performance degradation
BOM and routing complexity varies by manufacturing mode
Dolibarr ERP gotchas
Foreign key constraint errors on cross-distribution database restore
SQL injection vulnerabilities in version 9.0.1
Custom fields stored as JSON in extraoptions require field-by-field deserialization
Decimal precision and rounding configuration affects price fields
No native iOS/Android app forces reliance on browser
Pair-specific challenges
Migration approach
Schema audit and database access
We audit the Freedom ERP production database to identify all tables, columns, custom fields, and non-standard structures added during implementation. We confirm the database type (SQL Server version), confirm read-only access credentials, and map the Freedom ERP object model to our migration schema. If the instance is cloud-hosted, we coordinate with the customer's Freedom ERP vendor to grant direct database access. We produce a schema map listing every source table, its corresponding Freedom ERP module, and whether it maps to a standard Dolibarr object, extrafields, or a Dolistore module.
Dolibarr module selection and configuration
We configure the target Dolibarr instance: activate the CRM, Products, Stock, Invoices, Accounting, HR, and Projects modules; install the required manufacturing extension from Dolistore (selected by the customer based on our recommendation); and configure the chart of accounts for Indian GST compliance. We create extrafields for every mapped Freedom ERP custom field and configure the warehouse structure to match Freedom ERP's stores module. The Dolibarr configuration is validated in a sandbox environment before any data import begins.
BOM reconstruction and production order planning
We extract the full BOM tree from Freedom ERP—multi-level structures, component quantities, scrap rates, and phantom assemblies—and reconstruct it as Dolibarr-compatible assembly variants or BOM module entries (if installed). We also extract open production orders with their status, routing, and scheduling dates. This step runs as a planning-day workshop with the customer's production or planning team to confirm BOM decomposition accuracy before any import script is written.
Data extraction in dependency order
We extract data from Freedom ERP in dependency order: third parties (Customers and Vendors), items (with stock levels), BOM structures, chart of accounts, open AP/AR invoices, production orders, quality and maintenance records, employees, and payroll summaries. Large record sets are chunked by fiscal year and run during off-peak hours. Each export batch is validated against source record counts before the next phase begins. Custom fields export as supplementary columns alongside standard fields.
Sandbox migration and reconciliation
We run a full migration into a staging Dolibarr environment using production data volume. The customer's operations team reconciles record counts (Customers in, Vendors in, Items in, BOMs in, open invoices in, production orders in, employees in), spot-checks twenty to thirty random records against the Freedom ERP source, and signs off the schema, mapping, and module configuration. BOM decomposition accuracy is verified by comparing a sample of assembled item cost calculations against Freedom ERP's reported BOM cost. Any mapping corrections happen here, not in production.
Production cutover and handoff
We schedule a parallel-run cutover to minimize downtime: Freedom ERP remains writable until the delta migration runs (capturing any records created or modified during the migration window), then writes are frozen and the final delta is imported into Dolibarr. We deliver the full migration inventory document listing every workflow, alert, custom screen, and scheduled job in Freedom ERP that requires rebuild in Dolibarr's configuration tools. We do not rebuild Freedom ERP workflows as Dolibarr automations inside the migration scope; that work is handled by the customer's admin or a Dolibarr specialist.
Platform deep dives
Freedom ERP
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. All 8 core objects map 1:1 between Freedom ERP and Dolibarr ERP.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Freedom ERP and Dolibarr ERP.
Object compatibility
All 8 core objects map 1:1 between Freedom ERP and Dolibarr ERP.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Freedom ERP: Not applicable.
Data volume sensitivity
Freedom ERP doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Freedom ERP to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your Freedom ERP to Dolibarr ERP migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Freedom ERP
Other ways to arrive at Dolibarr ERP
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.