Migrate from Info.Net to Dolibarr ERP

Info.Net Items (finished goods, raw materials, and components) map to Dolibarr Product records with the type flag set to Product or Service. The Info.Net SKU maps to ref, description maps to label, unit of measure maps to unit of measure, and cost maps to cost_price. We migrate Items in a first pass before any BOM or Work Order imports so that Dolibarr's BOM module can resolve product references when loading Bill of Materials components.

Multi-level BOMs from Info.Net map to Dolibarr BOM records with the parent product linked as the finished product. Component lines map to BOM lines with quantity and unit of measure preserved. We handle revision versioning by creating separate BOM records per revision and linking the active revision to the production order. If Info.Net uses phantom BOMs or sub-assemblies, we replicate those as intermediate BOMs in Dolibarr with the correct self-referencing product type.

Info.Net Production Orders track manufacturing jobs with status, quantity, scheduled dates, and work center assignments. Dolibarr does not have a native Production Order object; we map these to Projects with custom fields carrying production status, quantity, scheduled start and end, and work center. If the customer activates the BOM module and Project module together, we link the Project to the relevant BOM so that component consumption can be tracked against the production run. Completion dates and scrap quantities from Info.Net migrate as custom fields on the Project record.

Info.Net Work Orders assign production tasks to employees or work centers with start/end dates and labor estimates. Each Work Order maps to a Task within its parent Project (mapped from the corresponding Production Order). Task status maps from Info.Net status, labor hours map to Task duration, and assigned employees map to Task assigned users. We preserve the full work order lifecycle including status transitions and actual labor consumed as notes or custom fields on the Task.

QC logs hold inspection results, pass/fail flags, and measurement data linked to production lots. Dolibarr does not have a native QC module in the core; we map QC data to Product extrafields (if inspection applies to the product level) or to Stock Shipment extrafields (if inspection applies at the receiving or shipping level). Measurement field names from Info.Net are mapped to extrafield keys we pre-configure in Dolibarr before migration. Lot or batch numbers migrate to Dolibarr's lot tracking module if activated.

Inventory movements (receipts, issues, adjustments, and transfers) in Info.Net carry timestamps, quantities, and locations. These map to Dolibarr Stock Movement records linked to the relevant Product (from the Item mapping). Post dates are preserved in the movement date field to maintain accurate stock valuation history. If Info.Net tracks stock by warehouse location, we pre-configure Dolibarr warehouses and map location codes before loading movements.

Info.Net Customer records include billing addresses, shipping addresses, and credit limits. In Dolibarr, customers and suppliers share a single third-party object where the type is set per record. We extract Info.Net Customers, create Dolibarr third-party records with type=Customer, and map billing address to the default address fields and shipping address to the shipping address fields. Multi-address customer accounts are resolved by creating address records in Dolibarr linked to the parent third-party.

Info.Net Vendor master records include contact details, payment terms, and lead times. These map to Dolibarr third-party records with type=Supplier. Address structures and multi-contact handling require field-level mapping because Info.Net and Dolibarr use different field names for supplier contact roles. We deduplicate any vendor records that share the same tax ID or email across the source export before inserting into Dolibarr.

Info.Net User accounts carry role assignments and permission sets. We map roles to equivalent Dolibarr permission groups (Admin, Read Only, Read/Write per module). We cannot preserve individual password hashes from Info.Net; users are notified of a password reset on first login to Dolibarr. We migrate user display names, email addresses, and role assignments as active Dolibarr User records.

Info.Net custom fields on Items, Customers, and Vendors require pre-configuration in Dolibarr using the extrafields system before migration. We extract custom field definitions during discovery, create matching extrafield entries in Dolibarr (with correct type: string, int, float, date, select, etc.), and then load custom field values during the respective object import. Any custom fields with no matching target in Dolibarr's extrafield schema are flagged in the discovery report for the customer's admin to decide whether to create a new extrafield or drop the data.

Info.Net production order status values (Draft, Released, In Progress, Completed, Closed) map to Dolibarr Project status values (Draft, Open, Closed, Archived) and a set of extrafield flags for manufacturing-specific states (Released, In Progress). We configure the status mapping during Dolibarr setup and apply it during the Project import phase.

Info.Net notes and attachments linked to Items, Production Orders, or Work Orders migrate as documents in Dolibarr's document management system, linked via ContentDocumentLink equivalents to the respective Product, Project, or Task. We extract files from Info.Net's document store during the discovery phase, rename them to a predictable convention (object_type_id_filename.ext), and upload them to Dolibarr's documents directory before linking them to the target records.