Migrate from IMPulse ERP to Dolibarr ERP

IMPulse ERP Items (finished goods, raw materials, semi-finished stock) map to Dolibarr Product records with type classification (Product or Service). Unit-of-measure conversions and cost layers migrate to Dolibarr's cost and price fields. Non-standard UOM definitions stored as IMPulse ERP custom fields migrate as ExtraFields on the Product record after the Product ExtraFields are pre-created in Dolibarr.

BOM structures migrate to Dolibarr BOM records with component line items and quantities preserved. Version-controlled BOM revisions in IMPulse ERP require explicit versioning extraction; we migrate all active BOM versions and flag any orphan component links where a component Item was not successfully extracted first. BOM must load after Product to satisfy the bom_product reference.

Open and closed production orders carry routing steps, work-center assignments, and by-product allocations. We migrate open production orders with a hold flag and close them in Dolibarr after BOM and routing dependencies resolve. Historical closed orders migrate as read-only records with a completed status. In-progress orders require coordination with the customer to freeze or complete the production run before extraction.

IMPulse ERP Work Center definitions (capacity, calendars, routing dependencies) map to Dolibarr User records with the Resource role enabled. Capacity and calendar data migrate to ExtraFields on the User record since Dolibarr's base User model does not carry production capacity fields natively. Dolibarr's manufacturing module's work station definition is used for machine-level capacity tracking if the customer requires it.

Warehouse definitions, bin structures, and stock-location mappings transfer 1:1. Stock quantity balances migrate as a separate stock movement ledger snapshot that posts to Dolibarr's stock warehouse records after the warehouse definitions are in place. Multi-bin locations require Dolibarr's stock-location feature to be enabled before the stock snapshot loads.

IMPulse ERP Customer master records and contact data migrate to Dolibarr Third Party records with the Customer checkbox enabled. Contact data (names, phone, email, address) migrates to linked Contact records via Dolibarr's contact module. Duplicate detection runs across the destination before final insertion using company name and email as dedupe keys.

IMPulse ERP Vendor master records and contact data migrate to Dolibarr Third Party records with the Supplier checkbox enabled. Remit-to addresses and payment terms from IMPulse ERP map to Dolibarr's payment condition and bank account fields. Contact-level data migrates to linked Contact records as with customers.

Outstanding customer invoices and credit memos require careful balance verification against the IMPulse ERP trial balance. We extract open amounts, aging buckets, and invoice dates, then validate total AR matches before final insertion. Dolibarr's invoice status is set to Open for unpaid migrated invoices. Customer references link to the Third Party records created in the customer migration phase.

Outstanding vendor invoices and credit memos migrate to Dolibarr Supplier Invoice records with status Open. We extract open amounts and aging buckets and validate that total AP matches the source trial balance after insertion. Currency alignment is verified against IMPulse ERP's multi-currency settings since Dolibarr's accounting module requires correct currency assignment per supplier invoice.

IMPulse ERP account codes, descriptions, and classifications (asset, liability, equity, revenue, expense) map directly to Dolibarr accounting account records. We enable Dolibarr's accounting module before loading and use the account type mapping to set Dolibarr's Account Type field. Intercompany accounts and consolidated account hierarchies may require parent-account re-mapping depending on the target chart structure in Dolibarr.

HR and Payroll module migration involves effective-dated compensation records, tax withholdings, and accrual balances. We handle these as a separate migration phase with HR-specific validation rules after the core ERP migration completes. Employee master records migrate to Dolibarr's Hr module Third Party records with the Employee type enabled. Compensation and accrual data migrate as ExtraFields on the employee record since Dolibarr's base HR module is lightweight compared to IMPulse ERP's payroll depth.

IMPulse ERP custom fields on Items, Customers, Vendors, and Production Orders migrate as Dolibarr ExtraFields. Each ExtraField must be created in Dolibarr before the parent object import runs so that the custom field columns exist in the target schema during CSV load. We extract the full list of custom field definitions during discovery, map IMPulse ERP field types to Dolibarr ExtraField types (varchar, int, datetime, select, chkbxlst), and apply the ExtraFields definition export to Dolibarr's llx_extrafields table before object migration begins.

Full transaction history is migrated selectively based on the customer's reporting and audit requirements and Dolibarr's import performance. We scope a date-range filter at discovery to limit the export to the period required, and we load historical entries as Accounting transactions (EcritureComptable) after the Chart of Accounts is in place. Entries are loaded in date order to preserve accounting period continuity.

IMPulse ERP project and job tracking data migrates to Dolibarr Project records with task breakdown preserved as Dolibarr Tasks. Project status, dates, and budget information transfer to Dolibarr Project fields and ExtraFields. If IMPulse ERP stores time tracking per project, those hours migrate as Dolibarr Task time records if the project's time-tracking module is enabled.