Migrate from Intact iQ to Dolibarr ERP

Intact iQ Customer records (with addresses, price lists, credit limits, and account statuses) map to Dolibarr Third Party records with the Customer type enabled. The Intact iQ customer account code becomes the ref (reference) field in Dolibarr. We resolve multiple customer addresses by creating Dolibarr address records linked to the same Third Party, using the address type field to differentiate. Credit limits migrate as a custom field or into the dedicated bank and credit management module if enabled in Dolibarr.

Intact iQ Supplier records (with contact details, payment terms, rebate agreements, and procurement history) map to Dolibarr Third Party records with the Supplier type enabled. Supplier payment terms migrate to the Payment Terms module in Dolibarr if that module is active. Rebate agreements require manual reconfiguration in Dolibarr's supplier pricing rules post-migration; we document the original rebate structure in the migration specification.

Intact iQ Contact records linked to Customers and Suppliers (holding roles, phone numbers, and email addresses) map to Dolibarr Contact records linked to the corresponding Third Party. The contact's role in Intact iQ maps to the Civility and Positon/Job fields in Dolibarr. We preserve the association back to the parent Customer or Supplier via Dolibarr's contact link table.

Intact iQ Stock Items carry complex relationships: BOM structures, variant codes, reorder levels, and ABC categories. We map Stock Item to Dolibarr Product with type=product for stocked items and type=service for non-stocked. Intact iQ BOM structures do not have a direct Dolibarr equivalent without the Manufacturing module; if that module is enabled, we map BOM to Dolibarr's MO (Manufacturing Order) structures. Variant codes map to Dolibarr product variants if the Variants module is active. ABC category assignments migrate as a custom field.

Open and historical sales orders from Intact iQ map to Dolibarr ThirdPartyModule Order records. We preserve order line items, pricing, and discount structures. Intact iQ order statuses (draft, confirmed, dispatched, invoiced, closed) map to Dolibarr ORDER_CLASSIFIED_* constants. Historical orders migrate as closed records; open orders migrate with their current status so that pending fulfilment can continue in Dolibarr. Dolibarr's price migration bug (GitHub #15770) is mitigated by validating that migrated selling prices match the source total after import.

Intact iQ Purchase Order records include supplier references, expected delivery dates, and line-level item assignments. They map to Dolibarr CommandesFournisseur (Supplier Order) records. Expected delivery dates migrate as the date_livraison field. Line items map to the OrderLine table with Product references resolved via SKU lookup. Closed purchase orders migrate as historical records; open POs migrate as active records requiring goods receipt in Dolibarr.

Chart of Accounts records carry account codes, types, and cost-centre assignments. Intact iQ's account code structure varies between configurations, so we validate the destination chart before mapping. Dolibarr's Accounting module must be enabled. If the customer uses multi-company or multi-branch accounting in Intact iQ, we map each branch's chart to a Dolibarr journal or sub-account structure and flag any accounts that require manual cost-centre configuration in Dolibarr's auxiliary accounting.

Outstanding invoices and credit notes require careful sequencing. We extract current open items from Intact iQ, map them to Dolibarr Facture (customer invoice) or FactureFournisseur (supplier invoice) records with status=open. Partial payments and credit allocations migrate as Payment records linked to the invoice. Dolibarr's Open invoices must have the validated status before payments can be recorded; we validate this sequencing during migration design.

Intact iQ User records include roles, branch assignments, and permissions hierarchies. We map users to Dolibarr User records by email match. Permissions require translation: Intact iQ's branch-level access controls map to Dolibarr's permission sets and per-module access flags. We flag any permissions that have no direct Dolibarr equivalent for manual admin configuration post-migration.

Custom fields added to any standard object in Intact iQ are stored in the database and require manual field mapping during scoping. We identify all custom field names, data types, and the objects they extend during discovery. Each custom field is pre-created in Dolibarr as an extrafields row before data migration begins. Multi-select or multi-value custom fields in Intact iQ map to Dolibarr's checkbox or varchar2 list types.

Branch and warehouse assignments on inventory, stock takes, and users require pre-migration validation. Intact iQ's multi-branch configuration has no single Dolibarr equivalent without the Multi-Entity module (commercial). If that module is not licensed, we map branches to Dolibarr Projects (for financial and project tracking), Product categories (for stock segmentation), or User teams. Mismatched branch hierarchies are resolved during scoping and documented in the mapping specification.

Document storage in Intact iQ uses an internal attachment layer not exposed via the REST API definition. We do not migrate attached documents programmatically. We recommend exporting them separately using Intact's native export or manual download before cutover, then copying to Dolibarr's documents directory and linking to records post-migration. We provide a file inventory listing documents by parent record type and ID to guide re-attachment.