Migrate from Freespace ERP to Dolibarr ERP

Freespace ERP Customer records map to Dolibarr ThirdParty with Type = Customer. Standard fields — name, contact details, billing address, payment terms — migrate 1:1. We scan the name field for non-alpha ASCII characters (symbols, special characters) before import and escape or strip them to prevent Dolibarr schema violations. Billing address maps to address fields; payment terms migrate as Dolibarr picklist values rather than free text.

Freespace ERP Vendor records map to Dolibarr ThirdParty with Type = Supplier. The same name-field sanitization applies (non-alpha ASCII stripping). Contact details, shipping address, and payment terms migrate as with customers. We validate that all vendor payment-term codes exist as picklist values in the target Dolibarr instance before import and flag any codes requiring custom picklist creation.

Freespace ERP Item masters — SKU, description, unit of measure, cost, and type (stock vs service) — map to Dolibarr Product records. The hs_sku or equivalent field becomes the Product reference code. Unit of measure mapping requires a lookup table because Freespace and Dolibarr use different default UoM codes; we normalize to a standard set during transform and flag any non-convertible units.

Freespace ERP multi-level BOM structures (where subassemblies reference their own child BOMs) require an explicit handling decision during scoping: flatten to a single-level explosion, or preserve as sub-assembly links using Dolibarr's BOM with assy_type set appropriately. Dolibarr's BOM module stores parent product, lines (child product + quantity), and cost calculation. If the source uses routing or work centers, we flag those for manual configuration post-migration.

Open Accounts Receivable — invoices, credit memos, and payment records — export from Freespace ERP with document date, due date, amount, and payment terms. We chunk documents by document date range to manage API response sizes, sequence rows by posting date, and preserve payment-term codes as Dolibarr picklist values. Partial payments attached to invoices migrate as separatePaiement records linked to the parent Facture.

Open Accounts Payable documents migrate to Dolibarr Facture with Type = Supplier. Document date, due date, amount, and payment terms follow the same picklist preservation logic as AR. We cross-reference vendor IDs against the migrated ThirdParty records to resolve supplier lookups before AP document import begins.

Freespace ERP organizes accounts around industry-specific modules rather than a generic chart of accounts, with cost-center assignments and dimensional tags. Dolibarr's accounting module does not use a traditional chart of accounts — instead, it records transactions directly against Bank Account records with journal entries. We map Freespace account codes to Dolibarr account codes where present, flag any cost-center assignments that cannot map to Dolibarr's flat account structure, and deliver a written decision document for your admin on how to handle dimensional reporting post-migration.

Freespace ERP journal entry headers and line items — account codes, debit/credit amounts, and dimensions — map to Dolibarr accounting entries. Line item sequence and dimension tags require field-level mapping to match Dolibarr's posting model. Large-volume historical journal entries are chunked by date range to prevent API timeout, and we validate that each journal entry balances (debits equal credits) before loading.

Freespace ERP transaction history includes production orders, material issues, and inventory movements — often high-volume exports requiring chunking by date range. These map to Dolibarr Stock Movement records (for inventory transactions) and Project Task records (for production order stages). We sequence entries by posting date and flag any transactions referencing items or accounts that failed the earlier object migrations.

Freespace ERP Employee profiles — name, department, job title, hire date, employment status — map to Dolibarr User records with the HR module activated. Custom employee properties added during Freespace onboarding are enumerated during scoping against the platform's field management UI and explicitly included in the export. Employment status (active/inactive/terminated) maps to Dolibarr's user active flag.

Freespace ERP compensation records carry effective-dated rows with pay frequency, salary or wage rates, and deduction codes. Retroactive adjustments can create rows where the effective date precedes the record creation date, producing non-sequential ordering. We flag these gaps, sort all compensation rows by effective date before importing, and flag any records with retroactive gaps for manual review. Pay frequency and deduction codes map to Dolibarr salary extra fields; a written inventory of unmappable deduction codes is delivered for admin configuration.

Freespace ERP multi-stage production orders — stage names, quantities, and material consumption links — map to Dolibarr Project Task records (with the Project module active) or to Sales Order/Order records depending on the customer's manufacturing flow model. Freespace's user-defined stage names are preserved in a custom field for reference; Dolibarr stage assignment happens at migration time based on the stage mapping defined during scoping.

Freespace ERP Work Orders map to Dolibarr Project Task records with the manufacturing reference stored in the task description or a custom field. Work order status, scheduled start and end dates, and assigned labor hours migrate directly. Any work order attachments (drawings, routing sheets) are noted in the attachment manifest for manual retrieval because the Freespace API does not expose a bulk download endpoint for binary assets.

Freespace ERP custom properties on standard objects may not appear in the default export templates. We enumerate all active custom field definitions during scoping against the platform's field management UI and explicitly include them in the export field list. On the Dolibarr side, extra fields are created before migration begins, with field type mapping (text, numeric, date, picklist) determined by the source field type. Complex custom properties with conditional logic are documented for manual rebuild in Dolibarr.