Migrate from Finesse ERP to Dolibarr ERP

Finesse Customer records with address, contact, payment terms, credit limits, and tax IDs map directly to Dolibarr Third-Party contacts of type 'Customer'. The s.RowID becomes the Dolibarr ref (external id for dedupe), and the Finesse customer name becomes t.nom. We preserve payment terms in the dedicated duree_reglement field and credit limits as a custom field since Dolibarr's default installation does not enforce customer credit limits.

Finesse Vendor master data (bank details, W-9 information, payment terms, ship-from locations) maps to Dolibarr Third-Party contacts of type 'Supplier'. Multi-address Finesse vendor records with separate ship-from locations are promoted into Dolibarr's addresses table with the 'shipfrom' address type. We preserve the Finesse vendor reference as Dolibarr's ref_supplier field.

Finesse GL account structure (account number, name, type, description, intercompany flags, active/inactive status) maps to Dolibarr's accounting_account table. Account types map from Finesse's account classification to Dolibarr's pcg_type (product, view, reconciliation). We preserve active/inactive status explicitly to prevent inactive Finesse accounts from appearing in Dolibarr's account selector dropdowns. Finesse multi-segment account structures map to Dolibarr's pcg_version with the first segment preserved as account number.

Finesse Items map to Dolibarr Products (product table with type=0 for goods). The Finesse item type (raw material, finished good, sub-assembly) becomes Dolibarr's fk_product_type. BOMs in Finesse map to Dolibarr's bom table (one BOM per finished item), restructuring multi-level Finesse BOMs into Dolibarr's flat single-level format: if Finesse has a three-level BOM, we create multiple Dolibarr BOM records and note the sub-assembly linkage for manual assembly order planning. Routings and work center data have no native Dolibarr equivalent; we preserve routing steps as a custom field (fk_ouv倒在gating in Dolibarr's production module if activated) and flag this as requiring partner configuration during user acceptance testing.

Finesse Projects (headers with status, cost variance, milestones) map to Dolibarr Project records. The Finesse project_status and cost_variance fields migrate to Dolibarr proj.description (as structured text) and custom fields (pct_variance__c). Project start and end dates map to proj.date_start and proj.date_end. We extract project-level milestone descriptions and map them to Dolibarr ProjectTask records with zero assigned hours to preserve the schedule structure. Note that Dolibarr's native project cost tracking is basic; customers needing ETO-style cost variance reporting should activate the project cost extension or use a custom field reporting approach.

Finesse Jobs (the manufacturing execution unit with start date, quantity, priority, and cost tracking) map to Dolibarr Production Order records (fk_product = finished item, qty = job quantity, fk_bom = linked BOM). Job priority and planned start date migrate to the production order's planned_start_date and priority custom fields. Line-level cost entries from Finesse (labor and material postings) aggregate into Dolibarr project task cost custom fields or note fields on the linked project, since Dolibarr production orders do not carry native cost breakdown at the line level. Customers with complex job cost variance reporting needs should plan for custom reporting or a BI extension.

Open Finesse AP invoices and credit memos migrate to Dolibarr facture_fourn (supplier invoice) records. We export open AP as line-item detail rather than summary balances to preserve aging accuracy in Dolibarr. Vendor references map to the supplier contact (t.rowid), payment terms to duree_reglement, and invoice due dates to date_lim_reglement. Any Finesse AP records with nested approval hold flags are flagged for manual review before destination activation. Finesse cost-distributed invoices (with cost center or WIP postings) require discussion during scoping: Dolibarr's supplier invoice lines do not natively support cost center splits without extension modules.

Open Finesse AR invoices, unapplied payments, and credit memos migrate to Dolibarr facture (customer invoice) records with full aging detail. We preserve the Finesse AR aging buckets as custom fields on the invoice for reconciliation. Any AR records with nested dispute or credit hold flags migrate as Dolibarr invoice status=demande_paiement (payment requested) with the hold flag preserved in a custom field and a note for the customer's billing admin to review. The customer contact reference (socid) resolves to the Dolibarr Third-Party contact created from the Finesse Customer mapping.

Finesse on-hand quantities by location and lot number migrate to Dolibarr stock_mouvement (stock movement) and warehouse inventory records. We extract the Finesse inventory valuation snapshot and create corresponding stock_reel entries per warehouse. Lot and serial number traceability migrates where Finesse tracks lot numbers, mapping to Dolibarr's lotindre object. We flag any negative quantities or quantities below Finesse safety stock levels as a pre-migration reconciliation item. Finesse's multi-warehouse locations map to Dolibarr's entrepot records.

Finesse user-defined fields on master and transaction records export with both their definition and values. We map Finesse field definitions to Dolibarr's extrafields database table (INSERT INTO llx_extrafields), creating each custom field with its type (varchar, int, datetime, text, select, etc.) before importing values into the corresponding llx_<object>_extrafields table. Custom field values for Customers, Vendors, Products, Projects, and Invoices are then loaded as part of the main data migration phase.

Documents stored in Finesse (drawings, specs, photos, PDF documents) are exported via file system copy or direct database BLOB export depending on the Finesse storage backend. We copy files to the Dolibarr document directory structure, creating ECM folders that mirror the Finesse document categories (e.g., /customer/, /project/, /item/). Each document record is created in llx_ecm_files with the entity, module, and ref linking to the parent Dolibarr record. Files older than the customer's retention window are flagged for manual review before migration. The migration admin configures Dolibarr's ECM module activation during the destination setup phase.

Finesse user records (login, roles, department assignments, security permissions) map to Dolibarr llx_user records. Login, first name, last name, email, and active status migrate directly. Finesse role names map to Dolibarr's rights structure via the llx_rights_def table, though role names differ: Finesse role-based permissions require manual mapping to Dolibarr's permission system (read/write/delete on per-module rights). Department assignments map as custom fields on User or as a separate Dolibarr department structure if the HR module is activated. Inactive Finesse users are exported with status=0 in Dolibarr for audit trail purposes.