Migrate from Infor VISUAL to Dolibarr ERP

VISUAL Customer master records map to Dolibarr ThirdParty with Role=customer. We extract customer name, addresses, credit limits, and EDI partner assignments. EDI trading partner configuration requires a separate extraction pass because VISUAL stores partner preferences (transaction set version, BOL formatting) in configuration records linked to but not stored in the customer master table itself. The customer role is set on ThirdParty.tousers and the customer code maps from VISUAL's cust_no field.

VISUAL Vendor master records map to Dolibarr ThirdParty with Role=supplier. Vendor payment terms, addresses, and EDI configuration extract alongside customer records in the same third-party pass. We flag duplicate vendor names that would create duplicate ThirdParty records in Dolibarr's unified schema.

VISUAL Item master records (SKU, description, unit of measure, cost, revision) map to Dolibarr Product. Standard cost from VISUAL becomes the-buyingprice in Dolibarr; selling price maps from the item's standard price record. Revision-controlled items may require multiple Dolibarr Product records or a custom ref_supplier field to track version history, depending on whether Dolibarr's multi-BOM-per-product feature is activated.

VISUAL's operation-scattered BOM structure (materials attached to routing operations rather than stored as a flat single-level or multi-level structure) requires reconstruction before loading into Dolibarr. We join BOM materials to routing operations by Work Order header and operation sequence number, then flatten them into either Dolibarr's multi-level BOM feature (if the production module is activated) or a Project with linked Task records representing each operation. We flag cases where VISUAL's just-in-time material release logic cannot be represented in Dolibarr's flat BOM model.

VISUAL Work Orders combine a production header, routing steps, and operation-linked materials. Dolibarr has no native work-order module. We split the Work Order into a Project record (header and scheduling metadata) plus Task records for each routing operation. Open production quantities, operation status, and actual-versus-estimated labor map to Project task fields. Completed Work Orders may be archived as Project records rather than imported as active production records if Dolibarr's production module is not activated.

VISUAL Routings define the sequence of operations and the resources (labor, machine, work center) each step requires. We map routing headers and operation details including setup and run times to Dolibarr Project Task records, preserving operation sequence as task rank. Work center references require a lookup table since Dolibarr does not have a native work-center concept; we use Project category or a custom field to represent the resource group.

VISUAL Customer Orders map to Dolibarr Propal or Commande (proposal/quotation and sale order). Order headers, line items, pricing, and EDI CPO data migrate directly. EDI-ready formats (ANSI X12 CPO transaction set) from VISUAL's fixed-length file exports map to Dolibarr's order line structure; the customer admin may need to re-enable EDI via a Dolibarr Marketplace module post-migration.

VISUAL Purchase Orders and associated ASN records (Advance Ship Notice, EDI 856) map to Dolibarr Supplier Proposal or CommandeFournisseur. ASN data extracts from VISUAL's fixed-length file exports and loads as order receipt records. We flag any ASN formatting preferences that would require a Dolibarr EDI module configuration after migration.

VISUAL invoices export as EDI 810 fixed-length files or through the Excel export background job. We map invoice header, line, and subline detail to Dolibarr Invoice. Custom invoice layouts or notes fields that do not map to standard Dolibarr invoice fields require post-migration template adjustment. Historical invoices that are posted and closed in VISUAL load as paid invoices in Dolibarr to preserve the accounting history.

VISUAL Employee records (HR module) including pay rates, departments, and cost center assignments map to Dolibarr User. Effective-dated compensation history from VISUAL requires mapping the current active record; we flag historical rate records that do not have a direct Dolibarr equivalent. Department and cost center assignments map to Dolibarr User category or project category depending on how the customer intends to use the field.

VISUAL GL account codes and descriptions export via the database export tool or Excel. We map account codes and descriptions to Dolibarr's accounting chart. Multi-company or intercompany account segments from VISUAL require segment-level mapping in Dolibarr's accounting configuration; we flag any destination-side account segment that needs segment-level setup before migration begins.

Open payables and receivables require careful balance verification during migration. We extract open invoice detail from VISUAL's AP and AR modules, apply payment status mapping, and flag records where partial payments have been made. The open balance becomes the remaining amount due in Dolibarr Invoice with a payment status of open.