Migrate from Blue Link ERP to Dolibarr ERP

Blue Link Customer records map to Dolibarr Third-Party (societe) records with the client checkbox enabled. We preserve customer contact details, multi-currency flags, credit status, payment terms, and sales rep assignment. Blue Link's credit limit maps to a custom field on the Dolibarr Third-Party record. Address records (shipping and billing) map to Dolibarr address contacts (contact object with type = invoice address or delivery address). Multi-currency flags in Blue Link require a check that the Dolibarr installation has the multi-currency module (multicurrency) enabled, which is a standard module but must be activated during Dolibarr setup before migration begins.

Blue Link Vendor records map to Dolibarr Third-Party records with the supplier checkbox enabled. Payment terms, multi-currency flags, and address records migrate in the same pattern as Customer records. We flag any vendor-to-PO linkage that requires re-establishment in Dolibarr because the parent PO record is not yet migrated at the time of vendor resolution. A cross-reference table linking Blue Link vendor IDs to Dolibarr Third-Party IDs is maintained throughout migration to support downstream PO linkage resolution.

Blue Link inventory items with a single unit-of-measure map directly to Dolibarr Product records. We map Blue Link item fields including SKU (ref), item description (label), item type (product or service), cost price (cost_price), selling price (price level mapping), reorder point, and weight or dimensions where present. The product type in Blue Link (stockable, service, kit) maps to Dolibarr's typent (0 = product, 1 = service). For lot-tracked Blue Link items, the lot numbers migrate as separate stock_lot records in Dolibarr if the third-party lot module is installed; we note this as a prerequisite module activation during scoping.

Blue Link customers commonly maintain duplicate inventory items to represent the same physical product with different UOMs (e.g., one SKU for each-of and one for case). We surface all duplicate UOM items during the data audit, present a consolidation strategy, and agree on an approach before migration: either consolidate to a single primary SKU and document the secondary UOMs for manual re-entry in Dolibarr, or if Dolibarr's product combination module (productbatch variant or a custom module) is available, we map the secondary UOM to a product combination attached to the primary product. This is the highest-risk mapping for data completeness on this pair and must be resolved before any inventory records are written to Dolibarr.

Open Sales Order headers and line items map to Dolibarr Commande records (type = 0 for customer order). We extract order header fields including order number, order date, customer reference, and sales rep assignment. Line items map to order lines with product reference resolution, quantity, unit price, and tax mapping. Open orders are sequenced as the final migration phase, extracted as close to Go-Live as possible to avoid the gap where an order ships between extraction and cutover. We run a delta validation check within 24 hours of Go-Live to catch any orders placed in the brief overlap window. Closed historical sales orders migrate as archived records if scope includes historical order data.

Open Purchase Order headers and line items map to Dolibarr Commande records (type = 1 for supplier order). We resolve the vendor reference via the cross-reference table built during vendor migration. Line items map with product reference, quantity, and cost price. PO-to-receipt linkage (partial receiving against a PO) does not carry forward automatically; we document each partially-received PO and advise the customer to receive remaining goods against the PO in Dolibarr post-migration. As with Sales Orders, open POs are migrated last, just before Go-Live, and a delta check is run within 24 hours of cutover.

Blue Link lot numbers associated with inventory items and shipment lines migrate to Dolibarr stock_lot records if the Dolibarr stock_lot module is installed and activated. We map the lot number, lot expiry date, and the linking stock movement records. If the customer does not have the stock_lot module installed, we flag this as a prerequisite and document the module activation steps; lot traceability cannot be preserved without it. Lot numbers tied to specific shipment lines require a separate stock movement record import to establish the lot-to-location linkage in Dolibarr.

Blue Link AR records (invoices, credit memos, and cash applications) map to Dolibarr Facture records (type = 0 for customer invoice, type = 2 for credit note). Open invoices retain their payment status (paid, unpaid, partially paid) as migrated to Dolibarr's PaiementFacture table. Collections history that exists in Blue Link as activity log entries does not migrate as discrete records; we document the collections notes as a custom field on the invoice record and advise the customer that collections activity history requires manual note entry or a separate process to re-establish in Dolibarr.

Blue Link AP records (vendor invoices, credit memos, and payment applications) map to Dolibarr Facture records (type = 1 for supplier invoice, type = 2 for credit note). Unpaid and partially paid invoices are flagged during migration so that open payables can be reconciled against the bank and paid in Dolibarr post-Go-Live. Blue Link's cash requirements and aging reporting is not a native Dolibarr standard report; we document the equivalent Dolibarr aged-receivable report (Comptabilite > Customers > Aged Creditors / Aged Debtors) and note that a third-party accounting module may be needed for the specific aging format the customer used in Blue Link.

Blue Link's Chart of Accounts structure migrates to Dolibarr's Accounting Account table (plan_comptable). Blue Link accounts flagged as expense, income, asset, liability, or equity map to Dolibarr account type fields (ptype). Custom account segments or departmental cost-centre dimensions in Blue Link do not map to a native Dolibarr equivalent in the base accounting module; if cost-centre reporting is business-critical, we flag this as a structural gap and recommend the third-party cost control module or a manual reporting workaround. Account numbers are validated against Dolibarr's allowed character set during transform; any non-conformant characters are replaced or flagged for manual correction before import.

Blue Link multi-warehouse and bin-level locations map to Dolibarr Entrepot records. Bin-level assignments (shelf, rack, location within a warehouse) do not have a native Dolibarr equivalent; if the customer relies on bin-level picking, we document the current bin assignments as a reference file and advise that a third-party warehouse management module or manual bin assignment workflow is required in Dolibarr. We also map the default warehouse assignment on each inventory item so that stock quantities associate with the correct warehouse immediately after migration.

Blue Link pulls orders from Shopify, Amazon, and eBay channels into its order management system. Historical eCommerce orders in Blue Link carry channel metadata (channel name, channel order ID, channel timestamp) that we preserve in custom fields on the migrated Dolibarr order record. Active channel integrations do not migrate; the customer must reconnect Shopify, Amazon, or eBay to Dolibarr post-migration using Dolibarr's eCommerce connectors or the DoliStore WooCommerce/PrestaShop modules. We deliver a written guide for reconnecting each channel with the correct webhook and API configuration.