Migrate from Spectrum ERP to Dolibarr ERP

Spectrum Jobs with their phase and cost-code hierarchy map to Dolibarr Projects. We preserve the Job number as the Project reference code and nest phases as Project tasks under the parent Project. Cost codes from Spectrum are stored as task-level custom fields in Dolibarr since Dolibarr has no native phase/cost-code structure. The customer's Dolibarr Project module must be enabled during configuration; if it is not, the migration uses Third-Party records with a project-type category instead.

Spectrum Work Orders link to Jobs and carry their own labor, materials, and equipment allocations. We split each Work Order into a Dolibarr Project task, preserving the work-order-to-job linkage through a parent Project reference. Labor and materials allocations migrate as task-level notes or custom fields. Equipment work order components require a separate mapping pass because Dolibarr has no native Equipment entity.

Spectrum G/L Account records map directly to Dolibarr accounting Account records. Account structure — including segments and rollup hierarchies — maps via a pre-migration mapping session where we define which Spectrum account segments correspond to Dolibarr account codes. The account type (asset, liability, equity, revenue, expense) is translated from Spectrum's account classification.

We extract both debit and credit lines of every Spectrum journal entry through the Add G/L Journal Entries web service, which surfaces both sides in a single call. This is migration-critical: without both sides, the Dolibarr trial balance will not reconcile. We load journal entries as Dolibarr AccountingDocument records, pairing debit and credit lines so that the sum of debits equals the sum of credits in the destination. Historical journal entries with no current open status are loaded as closed entries.

Spectrum A/R customer records map to Dolibarr Third-Party records with the Customer check box enabled. Open invoices migrate as Dolibarr CustomerProposal or Invoice records linked to the Third-Party. Historical paid invoices migrate as closed invoice records. Customer payment terms, credit limits, and address data transfer directly. The customer's currency setting in Dolibarr must be verified before AR migration because Spectrum may carry multi-currency customer records that Dolibarr's basic accounting handles differently.

Spectrum A/P vendor records map to Dolibarr Third-Party records with the Supplier check box enabled. Open purchase invoices migrate as Dolibarr SupplierProposal or Invoice records. Vendor payment terms, bank details, and W-9 or tax ID fields transfer to the Dolibarr Third-Party contact information section. Historical paid invoices migrate as closed records. Deduction codes specific to certified payroll or union rules may require manual remapping in Dolibarr's accounting settings post-migration.

Spectrum Employee records split into two Dolibarr record types: the personal and contact data migrates to a Third-Party record with the isStaff flag set, and the login credentials and system access data migrate to a Dolibarr User record. Certified payroll fields and union rule compliance flags are stored as custom fields on the Third-Party record since Dolibarr HR is a separate module that may or may not be activated. We flag which employees require User records versus Third-Party-only access during scoping.

Spectrum payroll data — pay stubs, pay groups, deduction codes, and union rule configurations — is one of the strongest areas of the source platform. We migrate pay stubs as Dolibarr accounting entries linked to the employee Third-Party record. Deduction codes require remapping in Dolibarr's accounting configuration because the code taxonomies differ between systems. Certified payroll compliance fields migrate as custom fields on the employee record. If the customer uses multi-union rule enforcement, the migration flags this as a post-migration configuration requirement since Dolibarr's native payroll module handles basic payroll but may require custom fields or community modules for advanced certified payroll workflows.

Dolibarr has no native Equipment entity, so Spectrum Equipment Tracking records are split: the equipment master data (description, ID, classification) migrates as a Dolibarr Product record with the IsInInventory flag set to treat it as a non-saleable asset. Preventive maintenance schedules and work order components migrate as Project tasks under a dedicated Maintenance Project. Any equipment-specific custom fields migrate as Product-level custom fields. The customer must decide during scoping whether to activate Dolibarr's Product module solely for equipment records or use a community-equipment module available on the Dolistore.

Spectrum's G/L Account structure with Excel template bulk export maps to Dolibarr's accounting Chart of Accounts via bulk import. Account rollup hierarchies are preserved as parent-child account relationships in Dolibarr. We run a pre-migration mapping session to confirm that Spectrum's account segment structure maps cleanly to Dolibarr's flat account numbering scheme. Multi-segment accounts in Spectrum may require flattening or segment concatenation during import.

Spectrum Inventory records migrate to Dolibarr Product with stock tracking enabled. Current stock levels, reorder thresholds, warehouse locations, and product categories transfer to the Dolibarr Stock module. Multi-warehouse configurations in Spectrum map to Dolibarr warehouses. Lot and batch tracking fields migrate as product-level custom fields if the customer uses those features in Spectrum.

Spectrum Service Request custom fields are limited to four per form. We extract all field definitions and current values during scoping and map them to Dolibarr's Extra fields (champs personnalisés) model, which supports more than four fields per entity. If the customer uses fewer than four custom fields, the mapping is direct. If the destination Dolibarr instance uses a community module for extended custom fields, we activate it during configuration before migration begins.

Project Log Images, Work Order Images, and Employee Images from Spectrum's Document Imaging web service migrate as Dolibarr documents attached to the corresponding Third-Party or Project record via the Document module. Binary image data requires a separate transfer pass after relational records are loaded to ensure attachments link to the correct parent. We preserve the original filename and upload date metadata during import.