Migrate from Adaptive to Dolibarr ERP

Adaptive Customer records (name, address, contact details, tax IDs) map to Dolibarr ThirdParty records with the Customer type flag set. We transfer the full address block as Dolibarr addresses and preserve tax registration numbers in the fiscal number field. Dolibarr supports a merged ThirdParty object that serves both customer and supplier roles; if Adaptive uses separate Customer and Supplier records, we create two distinct ThirdParty records with matching ThirdPartyType values. Any customer-specific custom fields are flagged for manual re-entry or custom field module configuration post-migration.

Adaptive Supplier records map to Dolibarr ThirdParty with the Supplier type flag. Payment terms and bank details transfer to Dolibarr's supplier payment conditions and BAN fields. If Adaptive stores supplier-specific price lists or purchase terms, these map to Dolibarr's SupplierPrice objects. We flag any multi-tier supplier hierarchies (parent vendor, sub-vendor) as requiring manual re-configuration in Dolibarr because the ThirdParty model is flat.

Adaptive's flat account codes with type flags require transformation to Dolibarr's PCG-compatible account plan structure. We extract the full account code, account name, and account type (asset, liability, equity, revenue, expense) from Adaptive and map to Dolibarr's account plan. For UK-hosted Adaptive deployments, account codes may use a non-PCG structure that requires manual mapping during discovery. Account codes longer than Dolibarr's 10-character limit require truncation or prefix preservation decisions made with the customer's finance team. Versioned ledger entries reference the original account codes; we preserve these as metadata in Dolibarr's account description field.

Adaptive open AP and AR invoices transfer as Dolibarr CustomerInvoice or SupplierInvoice records with status preserved as DRAFT, VALIDATED, or UNPAID. Line items map to Dolibarr invoice lines with quantity, unit price, and VAT mapping. Outstanding balance is preserved in the payable or receivable amount field. We explicitly flag which invoices have partial payments so that Dolibarr's payment scheduling feature can be configured post-migration. Invoice PDFs from Adaptive transfer as document attachments linked to the invoice record in Dolibarr's documents folder.

Adaptive journal entries carry fiscal period and date metadata that must map to Dolibarr's accounting year and period model. We flag any entries that span Dolibarr's fiscal year boundaries because period re-assignment during import affects audit trail continuity. If Adaptive uses a non-calendar fiscal year, we configure Dolibarr's fiscal year settings before migration begins. Historical entries without open balances migrate as closed accounting entries; entries with outstanding amounts retain their open status and link to the corresponding invoice or supplier record.

Adaptive Stock Items (SKU, description, unit cost, current quantity) map to Dolibarr Product records with the Stock Management module activated. We transfer the SKU as the product reference code, description as product label, and unit cost as the cost price field. Current warehouse quantities transfer to Dolibarr's stock levels per warehouse using the multi-warehouse module. We flag BOM (Bill of Materials) structures, batch numbers, and serial tracking for manual rebuild in Dolibarr because these require product-specific configuration that depends on the destination module activation state.

Adaptive document attachments (invoices, purchase orders, statements) stored as file references or blobs migrate as files transferred to Dolibarr's documents directory, linked via Dolibarr's document management model to the parent record (Customer, Supplier, Invoice, Product). We preserve the original filename and transfer date. Files exceeding Dolibarr's typical size limits are flagged separately for customer review. Dolibarr's document versioning is not native; we document the attachment structure for the customer's admin to configure document management post-migration if required.

Adaptive User accounts (name, email, role assignments) map to Dolibarr User records. We resolve users by email match and transfer the Dolibarr permission set corresponding to the Adaptive role level. Inactive or archived Adaptive users are held in a reconciliation queue because Dolibarr's user model requires explicit active/inactive status. Role mappings are approximate because Adaptive and Dolibarr use different permission models; we document the mapped permission set and flag any gaps for the customer's admin to review.

Adaptive custom field extensions stored against any standard object require Dolibarr's CustomFields module activation and configuration post-migration. We document every custom field found in the Adaptive schema (field name, data type, object attachment, sample values) in a written handoff document. The customer's admin activates the CustomFields module in Dolibarr, creates matching custom fields, and re-populates values using the migration export as reference. This is a post-migration manual step because custom field structures cannot be migrated as schema without a compatible module in the destination.

If Adaptive contains Project records, these map to Dolibarr Project objects. Dolibarr allows project associations to be visible directly on invoice pages, a feature reviewers note as valuable for tracking billed versus unbilled project time. Task structures map to Dolibarr Tasks under the Project. We flag any project-specific billing rates or time-tracking configurations for manual review because Dolibarr's project billing requires module activation and configuration specific to the customer's invoicing workflow.

Adaptive workflow metadata attached to records (status flags, approval states, custom workflow rules) has no direct Dolibarr equivalent without third-party automation modules. We document every workflow state machine found in the Adaptive schema, including trigger conditions, state transitions, and actions, in a written inventory delivered to the customer's admin. Rebuild options in Dolibarr include the native action system (limited), third-party automation modules from the Dolistore marketplace, or external tools. This is a rebuild scope, not a migration scope.

Adaptive multi-currency customer and supplier balances require Dolibarr's multi-currency module activation before migration. We transfer the base currency amount and the original currency amount; if Dolibarr's multi-currency module is not activated, we default to the base currency and flag the original currency amount for manual re-entry. Exchange rate history from Adaptive transfers as reference data in the Dolibarr multi-currency rate table.