Migrate from Infor SyteLine / Infor CloudSuite Industrial to Dolibarr ERP

SyteLine Customer records map to Dolibarr Third Party (type Customer). The SyteLine custaddr, payment terms, credit limit, and sales territory fields map to Dolibarr's address fields, condition_reglement, and mode_reglement. SyteLine's CRM attributes (credit status, account manager) map to Dolibarr's customer category and commercial fields. Multi-site SyteLine customers with separate billing or shipping addresses require Dolibarr address extensions or multiple Third Party records per site.

SyteLine Vendor records map to Dolibarr Third Party (type Supplier). SyteLine's vendor address, banking details, and purchasing terms map to Dolibarr's corresponding fields. Vendors must be imported before Purchase Orders in both systems to satisfy referential integrity. SyteLine's vendor code becomes Dolibarr's siret or barcode field for deduplication.

SyteLine Item records (stocked, non-stocked, service, and labor items) map to Dolibarr Product. SyteLine item types (Stockable, Service, Assembly) map to Dolibarr's type (Product, Service). Unit of measure from SyteLine's UM table maps to Dolibarr's units of measure. Cost layers (standard, average, last) migrate as Dolibarr pmp (weighted average price) and cost price fields. The price levels from SyteLine's price form map to Dolibarr customer price supplements or multi-currency price lists.

SyteLine BOMs (multi-level with operations and work centers) have no native Dolibarr equivalent. Dolibarr lacks a production work-order and routing engine. We assess the customer's BOM use case: for simple kitted products (sell-as-a-bundle), we create Dolibarr Products of type 'kit' with the BOM lines as sub-product lines. For manufacturing work orders requiring scheduling and labor tracking, we map BOMs to Dolibarr Projects with task lines carrying the component items and estimated hours. Customers needing full BOM-driven production scheduling will need to evaluate Dolibarr's third-party MRP plugins (e.g., Dolibarr-MRP module) or accept a process change.

SyteLine Jobs (production work orders linking materials, labor, and operations) map to Dolibarr Projects. The Job header (job number, status, start date, completion date) becomes the Project record. Job materials map to Project line items referencing Products. Job operations and labor hours map to Project tasks with time-tracking entries. Job completions and scrap data map to task completion percentages and notes. Closed Jobs migrate as Projects with status Closed; open Jobs migrate as active Projects. SyteLine Job-to-Sales-Order linkages migrate as Project-to-Commercial-Proposal links.

SyteLine Sales Orders map to Dolibarr Customer Orders. The order header (customer reference, order date, terms) maps directly. Line items map to Order lines with Product references resolved from the Items migration phase. Pricing, discounts, and delivery schedules migrate to Dolibarr order lines and date fields. Blanket orders with scheduled releases map to Dolibarr shipments linked to the parent order. Open orders migrate with status in progress; completed orders migrate as closed.

SyteLine Purchase Orders map to Dolibarr Supplier Orders. Vendor references resolve from the Vendors migration phase. PO line items map to Dolibarr lines with Product references. Quantities, prices, and due dates migrate directly. Blanket POs with release schedules map to Dolibarr shipment receipts linked to the parent order. SyteLine's approval workflow status maps to Dolibarr's order status field.

SyteLine Quotes generated via CPQ or manual entry map to Dolibarr Commercial Proposals. Quote headers, customer references, and configuration lines migrate. SyteLine's product configuration data (Configure-to-Order selections) migrates as Proposal line notes or as linked Product configurations depending on configuration complexity. Expired quotes migrate as closed proposals; active quotes migrate as open proposals with their expiration dates.

SyteLine's GL structure (account codes, descriptions, account types, sub-account segments) maps to Dolibarr's Account Plan (plan_comptes). SyteLine's multi-company or multi-entity chart segments map to Dolibarr's journal or accounting configuration per entity. The migration preserves account type (Asset, Liability, Equity, Income, Expense) and the full segment structure for cost-center or department reporting. Dolibarr's accounting module must be activated before COA import.

SyteLine Employee records (name, department, job title, and compensation where the HR module is active) map to Dolibarr User records. Department and job title migrate as Dolibarr User properties and group assignments. SyteLine employee costing rates map to Dolibarr cost accounting fields. Users must be provisioned in Dolibarr before importing any records where OwnerId references apply.

SyteLine custom fields stored as extended SQL columns on any master or transactional table map to Dolibarr extrafields. We inspect SyteLine's full column set for each exported table, identify user-defined columns, and map them to Dolibarr extrafields with equivalent types (string, int, date, select, checkbox). SyteLine-specific enumerated lists require value-mapping tables; these are documented for customer review before migration commits.

SyteLine open receivables and payables map to Dolibarr Customer Invoices and Supplier Bills. Customer invoice header, line items, amounts, due dates, and payment terms migrate with status Open. SyteLine payment terms and invoice aging data map to Dolibarr's payment condition fields. Closed invoices migrate as paid. Partially applied credit memos migrate as Credit Notes linked to the parent invoice.