Migrate from Focus ERP to Dolibarr ERP

Focus ERP account codes and descriptions, including parent-child hierarchies and segment columns, map directly to Dolibarr's Account object. We preserve account codes exactly and map Focus ERP account types (asset, liability, equity, revenue, expense) to Dolibarr's account categories. Multi-segment account codes are flattened or split into the appropriate number of sub-account fields based on the customer's chart design.

Focus ERP customer records with billing addresses, payment terms, and tax registration numbers map to Dolibarr Third Party (type Customer). We deduplicate on name-and-address composite keys where multi-company instances create duplicate customers. Payment term codes are mapped from Focus ERP's terms table to Dolibarr's payment condition labels.

Focus ERP vendor master records map to Dolibarr Third Party (type Supplier) with the same deduplication logic as customers. Supplier-specific fields such as supplier catalog reference and default lead times are preserved as extrafields on the Dolibarr Third Party object.

Outstanding payable records carry invoice numbers, due dates, and outstanding amounts. We extract open items with full payment history and flag partial payments and credit memos requiring split-line treatment. Each open AP item maps to a Dolibarr Supplier Invoice (status unpaid or partially paid), and the customer confirms the intended resolution for any split lines before we commit the load.

Outstanding receivable records carry invoice numbers, due dates, and outstanding balances. We apply the same extraction logic as AP: full payment history captured, partial payments flagged, and credit memos requiring explicit customer confirmation before load. Invoices are linked to the corresponding Third Party (Customer) already migrated in the previous phase.

Item masters with SKUs, descriptions, cost prices, selling prices, and stock levels export directly to Dolibarr Product records with the Stock module enabled. Where Focus ERP min/max replenishment rules were configured, we preserve those as extrafields in Dolibarr since native reorder management is simpler. Barcode and lot tracking fields map to Dolibarr's product lot and serial number tables if those modules are activated.

Open purchase orders map to Dolibarr Supplier Orders. Line-item tax codes and discount percentages from Focus ERP require explicit value-mapping because tax rate configurations differ by country setup in both systems. We stage the mapping table before the first load batch and present it for customer review.

Open and historical sales orders map to Dolibarr Customer Orders with the same tax and discount value-mapping step as purchase orders. Order status in Focus ERP (confirmed, in-progress, closed) maps to Dolibarr order statuses (Draft, Validated, On Hold, Closed) via a status translation table.

Focus ERP field-service and job-tracking records carry custom status workflows, technician assignments, and job-percentage progress fields. Each Focus ERP work order maps to a Dolibarr Project with Tasks representing sub-jobs or line items. Status values are translated via the mapping table, and technician assignments map to Dolibarr Project contact assignments. The customer chooses which active work orders are migrated versus re-created post-migration based on their job lifecycle stage.

Asset registers include acquisition dates, depreciation methods, and book values. Depreciation schedules require recalculation in Dolibarr based on its fiscal year settings, so we extract the asset register with the original depreciation method and book value at migration date and allow Dolibarr to recalculate from the migration date forward. This avoids carrying legacy depreciation schedules across platforms with different calculation engines.

Focus ERP user accounts export from the user table with their role assignments. Role naming conventions differ between Focus ERP versions and Dolibarr's permission model, so we map role names to equivalent Dolibarr permission groups rather than attempting a 1:1 role name match. Users are provisioned in Dolibarr with their permissions set to match the functional access level of the original Focus ERP role.

Custom fields added via Focus ERP's form builder are stored in extended tables. We extract these as key-value pairs and attach them as Dolibarr extrafields on the corresponding object. Fields that use non-standard data types (e.g., custom picklist values, cross-referenced fields) are reviewed individually and mapped to the closest Dolibarr equivalent type (varchar, int, select, or link) before the load.

Focus ERP's multi-company structure with allocation ratios is a proprietary feature with no direct Dolibarr equivalent. We decompose the multi-company structure into separate Dolibarr Third Party records (one per cost center) and attach allocation ratios as numeric extrafields. The customer determines whether to rebuild automated allocation rules post-migration using Dolibarr's accounting configuration or a third-party module from the Dolistore.

Transaction histories and journal entries are extracted in dependency order: account codes are established first, then transaction lines post in chronological sequence. Each journal entry line maps to a Dolibarr AccountingRecord linked to the corresponding account. We flag any entries that reference a non-migrated account code for manual resolution before committing that batch.