Migrate from Infor CloudSuite Corporate to Dolibarr ERP

Infor CloudSuite uses a hierarchical COA with cost center and department rollups across multiple companies. Dolibarr uses a flat account structure with categories and subcategories but no native cost center or department dimension. We flatten the Infor hierarchy into Dolibarr account codes, preserving the parent-child relationships as account code prefixes or Dolibarr categories. Multi-company Infor setups require consolidation into a single Dolibarr company; we assess whether the customer's multi-site reporting can be handled via Dolibarr's category-based reporting before migration.

Infor Customer master records map directly to Dolibarr Third Parties of type Customer. We extract the address book (address, city, country, phone, email), payment terms, credit limit, and tax registration codes. Infor's Customer and Vendor masters are separate objects; Dolibarr combines them into a single Third Party entity with a type flag. We split accordingly during the transform. The Infor Customer ID becomes the Dolibarr ref_int or siret field for traceability.

Infor Vendor master records map to Dolibarr Third Parties of type Supplier. Vendor payment terms, bank details, and tax registration codes transfer to Dolibarr's Supplier configuration fields. Any Vendor-specific custom fields (defined as extrafields in Infor) require manual creation in Dolibarr before import; we include the field inventory in the pre-migration checklist.

Infor Items map to Dolibarr Products (for physical goods) or Services (for non-stock items). UOM conversions, costing method, and category assignments transfer to Dolibarr's unit settings, cost price, and category structures. Infor's warehouse-specific stocking data is not native in Dolibarr; we map the primary warehouse to Dolibarr's stock location and note any multi-warehouse data that requires manual reconciliation post-migration. BOM linkages and routing data do not migrate because Dolibarr has no BOM or routing module.

Open receivables from Infor CloudSuite are extracted as invoice headers and lines with payment terms and aging data. We load them into Dolibarr as Draft or Unpaid Customer Invoices. Infor's distribution records (invoice-to-GL linkages) require manual verification after load because Dolibarr tracks receivables at the invoice level rather than the distribution level. Open AR aging is recomputed from Dolibarr's payment terms after migration.

Open payables from Infor CloudSuite extract as supplier invoice headers and lines. We load them into Dolibarr as Draft or Unpaid Supplier Invoices. Infor's AP distribution records (invoice-to-GL cost allocation) require manual reconciliation post-migration. Any pre-payments or down payments tracked in Infor map to Dolibarr's advance payment mechanism if the customer activates the module; otherwise they are flagged as a manual post-migration task.

Infor Purchase Agreements include vendor, terms, expiration, and line-level pricing conditions. Dolibarr does not have a native Purchase Agreement object. We assess whether the customer's active agreements should become Dolibarr Proposals (to send to vendors) or be tracked as PDF attachments in Dolibarr's document management. Line-level pricing conditions that are non-standard are flagged for manual review. The migration scope for Purchase Agreements is configurable based on the customer's operational workflow preference.

Infor projects map to Dolibarr Projects. Project status, dates, description, and task hierarchy transfer directly. Dolibarr's project module is basic compared to Infor's project management capabilities; milestone tracking, resource allocation, and project budgeting require evaluation of Dolibarr's available modules before migration. We flag any Infor project fields that have no Dolibarr equivalent and document them in the field gap report.

Infor Work Orders carry routing steps, material allocations, and status. Dolibarr has no manufacturing, work order, BOM, or routing module. This is the most significant functional gap in the migration. We do not migrate Work Orders. We include a written inventory of all open Infor Work Orders at migration time with a note that these require a separate production system migration or manual closure. Organizations that rely on production planning in Infor should not proceed with this migration path.

Infor Document Management stores attachments against customer orders, purchase orders, and work orders as configurable widgets. We migrate the association metadata (which document links to which record in Infor). The actual binary files must be exported from Infor separately and reimported into Dolibarr's document management. We include a document inventory step in the migration plan and schedule a separate file reimport window before cutover. Binary file content migration is outside the standard scope.

Infor user accounts and role profiles require reconstruction in Dolibarr's user and group permission system. We extract the Infor role profiles and role-permission mappings during discovery. In Dolibarr, we create matching user accounts and assign them to permission groups. Dolibarr's permission model is module-based (each module has read/write/admin flags per user group); we map Infor role capabilities to Dolibarr permission group settings. Inactive Infor users become inactive Dolibarr users.

Infor CloudSuite custom fields (alphanumeric, numeric, date) attached to items, suppliers, and purchase agreements require manual recreation as Dolibarr extrafields. Infor edition-specific naming (Technical Datasheet in Industrial, Custom Fields in CMS470) is normalized during the inventory. We deliver a field-by-field map of every Infor custom field with its Dolibarr module target, field type, and display configuration. Extrafield group assignments in Dolibarr are configured manually before the data migration phase begins.