Migrate from CREST ERP to Dolibarr ERP

CREST ERP Customer master records (contact details, addresses, credit limits, payment terms) map 1:1 to Dolibarr ThirdParty records in Customer mode. The primary contact maps to a separate Contact record linked by SOCKET. We use the customer code or name as the dedupe key during import. Any custom properties on the Customer object require a pre-migration custom field enumeration phase because CREST ERP lacks a systematic export mechanism for custom field definitions.

CREST ERP Vendor master records (supplier details, bank information, performance ratings, purchase terms) map 1:1 to Dolibarr ThirdParty records in Supplier mode. Vendor-supplied catalogue items migrate as product references linked to the supplier. We validate that bank account details and payment terms transfer cleanly because Dolibarr stores these in dedicated sub-fields on the ThirdParty record.

CREST ERP Item masters (SKU, description, pricing, UOM, BOM data, routing) map to Dolibarr Product records. Items flagged as manufactured map with BOM structures preserved as Dolibarr BOM records linked to the parent Product. Routing data migrates as manufacturing order templates. Multi-level parent-child BOM relationships require a tree-walking transform during migration to construct the correct BOM bill-of-materials structure in Dolibarr.

The CREST ERP chart of accounts maps directly to Dolibarr Account records. Account codes, names, account types (asset, liability, equity, income, expense), and cost center assignments transfer cleanly. Intercompany account mappings require a manual review during the discovery phase. We create Dolibarr Account records before any AP or AR migration so that account lookups resolve correctly at insert time.

Open AP records (vendor association, invoice number, amount, due date, payment status) map to Dolibarr FactureFournisseur records in draft or open status. We identify which invoices remain open at migration cutover to avoid re-importing satisfied records. CREST ERP's payment terms and aging bucket data transfer to Dolibarr's payment schedule fields and invoice aging report. Credit memos and debit notes require offset handling via Dolibarr's credit note workflow.

Open AR records (customer association, invoice number, amount outstanding, aging bucket) map to Dolibarr Facture records in open status. We flag credit memos and partial payments for correct offset handling using Dolibarr's credit note mechanism. Customer invoice PDFs migrate as ContentDocument records linked to the Facture. Aging bucket data populates Dolibarr's outstanding balance fields for immediate reporting at go-live.

CREST ERP Sales Orders (customer linkage, line items, quantities, pricing, delivery dates, fulfillment status) map to Dolibarr Commande records. Order status from CREST ERP (Pending, Confirmed, In-Production, Shipped, Closed) maps to Dolibarr OrderStatus values. Line items migrate with resolved Product references. CREST ERP's SFA pipeline stages map to Dolibarr Project status or a custom order workflow if the customer uses Dolibarr's project module for sales tracking.

CREST ERP Purchase Orders (vendor linkage, line items, quantities, pricing, expected delivery dates, receipt status) map to Dolibarr CommandeFournisseur records. Receipt status from CREST ERP transfers to Dolibarr's reception workflow. Purchase approval chains configured in CREST ERP are documented during discovery and flagged for manual recreation in Dolibarr because CREST ERP's workflow configurations are not accessible via export.

CREST ERP Project records (budget, resource assignments, tasks, milestones, time entries) map to Dolibarr Project records. CREST ERP's configurable project templates migrate as Dolibarr Project templates if the project module is activated. Time entries attach to ProjectTask records with the employee reference resolved via the User mapping. Milestone data transfers as ProjectTask with a dedicated task type for milestone tracking.

CREST ERP Fixed Asset records (acquisition cost, depreciation schedule, asset category, location, maintenance history) map to Dolibarr Asset records. Depreciation methods (straight-line, declining balance) map to Dolibarr's asset depreciation configuration. We generate asset requirement records during migration and validate that acquisition dates and book values match the source totals before finalizing. Maintenance history migrates as linked intervention records if the Dolibarr intervention module is activated.

CREST ERP Employee records (personal details, job role, compensation history, PTO balances, attendance data) map to Dolibarr User records for system login and Contact records for HR data. Compensation history and PTO balances migrate as Dolibarr HR module entries or as custom fields on the Contact record depending on which Dolibarr HR module version is installed. Effective-dated pay period records require sequencing to preserve the chronological order of compensation changes.

CREST ERP Department structure (department codes, names, parent-child hierarchy) maps to Dolibarr UserGroup records for access control and Category records for organizational classification. We validate that cost center assignments on GL accounts align with the migrated department structure. If CREST ERP uses departments as project assignment buckets, we cross-check with the Project mapping to ensure consistency.

Historical GL journal entries, inventory movements, and production transactions migrate in reverse-chronological order with date-preserved posting timestamps. Multi-year histories carry significant volume; we chunk these into batches of 5,000 records per run with a reconciliation count after each batch. CREST ERP production transaction records require the Dolibarr manufacturing module to be active before import begins. Historical records that reference GL accounts or inventory items that were later deleted in CREST ERP are flagged in a pre-migration audit and held for customer resolution before the historical migration run.