ERP migration
Field-level mapping, validation, and rollback between Syscom ERP and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
Syscom ERP
Source
Dolibarr ERP
Destination
Compatibility
8 of 12
objects map 1:1 between Syscom ERP and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Syscom ERP to Dolibarr is an extraction-constrained migration. Syscom ERP does not publish a public REST or SOAP API in our research, so we rely on direct database export (SQL Server) or CSV-based extraction from the application's built-in export functions for each active module. The modular Syscom ERP8 architecture means every customer has a different module set in production, and we inventory those modules during discovery before scoping the object set. Dolibarr's modular architecture then receives the migrated data into whichever modules are enabled: Products for Items, Third-Party for Customers and Vendors, Orders and Proposals for sales documents, Stock for inventory, and Accounting for GL Accounts. We do not migrate Workflows, automations, or reports as code. We deliver a written inventory of Syscom ERP configurations for Dolibarr admin rebuild.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Syscom ERP object lands in Dolibarr ERP, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Syscom ERP
Item / Product Master
Dolibarr ERP
Product
1:1Syscom ERP item records (SKU, description, unit of measure, cost, and pricing tiers) map to Dolibarr Product records. We extract standard item fields and map unit of measure to Dolibarr's unit-of-measure field. Custom properties on items require pre-migration review to determine whether they map to Dolibarr extrafields or product subtypes (Simple Product vs Service). Product variants in Dolibarr require the Variants module to be enabled.
Syscom ERP
Bill of Materials (BOM)
Dolibarr ERP
BOM / Bill of Materials
lossySyscom ERP multi-level BOM structures with component items and quantities map to Dolibarr's BOM module if enabled. BOM versions and alternative BOMs require explicit mapping because Dolibarr's BOM module handles single-level explosion. We extract the full BOM hierarchy and document multi-level parent-child relationships in a separate handoff sheet if the customer's manufacturing process relies on nested BOMs beyond what Dolibarr's BOM module visualizes. Routing and work center data from Syscom ERP maps to Dolibarr Project tasks or a manufacturing notes field.
Syscom ERP
Customer / Account
Dolibarr ERP
Third Party (Customer)
1:1Syscom ERP customer records (billing address, shipping address, contact details, credit limits) map to Dolibarr Third Party records with the Customer subtype. Customer-specific pricing that exists in Syscom ERP migrates to Dolibarr's price list or special price rules per third party. We preserve customer codes as Dolibarr's code field for reference integrity.
Syscom ERP
Vendor / Supplier
Dolibarr ERP
Third Party (Supplier)
1:1Syscom ERP vendor records (contact information, payment terms, bank details) map to Dolibarr Third Party records with the Supplier subtype. Vendor-specific notes or custom fields require pre-migration review. Bank details from Syscom ERP map to Dolibarr's Rib field on the supplier record.
Syscom ERP
Sales Order
Dolibarr ERP
Order
1:1Syscom ERP sales order headers and lines migrate to Dolibarr Customer Order (Commande Client). Line-item detail, pricing, quantities, and order status (draft, validated, shipped, closed) map directly. We extract open orders as the primary scope and handle historical closed orders as a separate archival pass if the customer requires them. The Order reference number from Syscom ERP becomes the Order ref_customer field in Dolibarr.
Syscom ERP
Purchase Order
Dolibarr ERP
Supplier Order
1:1Syscom ERP purchase order headers and lines migrate to Dolibarr Supplier Order (Commande Fournisseur). Vendor reference, expected delivery date, and line-item detail preserve. PO status (open versus closed) maps to Dolibarr's order status workflow. We handle multi-currency PO amounts by mapping the Syscom ERP currency code to the corresponding Dolibarr currency configuration before the load.
Syscom ERP
Work Order / Manufacturing Order
Dolibarr ERP
Project / MRP
lossySyscom ERP work orders with BOM references, production quantities, operation sequences, and production status map to Dolibarr Project records with task breakdowns. If the MRP module is enabled in Dolibarr, production tracking maps to MRP Production objects. We note that Dolibarr's MRP module is less manufacturing-depth-focused than a dedicated ERP, so manufacturing-specific fields (routing steps, work center capacity) are documented in the handoff sheet for admin configuration post-migration.
Syscom ERP
Inventory / Stock
Dolibarr ERP
Stock
1:1Current inventory balances extract at the warehouse and bin level from Syscom ERP. We map location codes to Dolibarr warehouse records and load on-hand quantities and unit costs. Inventory transaction history (stock movements, adjustments) migrates as Dolibarr Stock Movement records if the stock history scope is agreed upon during discovery; otherwise, only current balances move. Multi-warehouse configurations in Syscom ERP map to multiple Dolibarr entrepots.
Syscom ERP
GL Chart of Accounts
Dolibarr ERP
Account (Accounting)
1:1Syscom ERP chart of accounts (account codes, names, types, parent hierarchy) maps to Dolibarr Accounting Plan entries. Active versus inactive status preserves. If Syscom ERP uses a multi-entity structure, we map each entity's chart of accounts to a separate Dolibarr accounting configuration. Currency gains and losses accounts for multi-currency must be explicitly identified during field mapping because Dolibarr's default chart may use different account codes for unrealized currency positions.
Syscom ERP
User / Employee
Dolibarr ERP
User
1:1Syscom ERP user accounts (login, roles, permissions) map to Dolibarr User records. We extract roles and map them to Dolibarr's permission groups. Dolibarr's permission model is module-based (access granted per module), so we document which Syscom ERP roles correspond to which Dolibarr module access grants during the mapping phase. Users without a corresponding Dolibarr login go to a reconciliation queue.
Syscom ERP
Custom Objects / User-Defined Fields
Dolibarr ERP
Extrafields (extra fields)
lossySyscom ERP user-defined fields vary by module and customer configuration. We identify all custom fields during discovery and map them to Dolibarr extrafields on the corresponding objects (ThirdParty, Product, Order, etc.). Dolibarr extrafields are typed (string, integer, select, date, checkbox) and must match the source field type during mapping. Complex custom objects that have no Dolibarr equivalent are documented in the handoff sheet for admin review.
Syscom ERP
Multi-Currency Configuration
Dolibarr ERP
Multi-Currency Setup
lossySyscom ERP multi-currency setup (currency codes, exchange rate tables, and currency gains/losses accounts) maps to Dolibarr's multi-currency accounting configuration. We extract exchange rates as of a agreed point-in-time and load them into Dolibarr's currency rate table. Any currency gains and losses accounts referenced in Syscom ERP that do not exist in Dolibarr's default chart of accounts are flagged for account creation before the currency-enabled entities load.
| Syscom ERP | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Item / Product Master | Product1:1 | Fully supported | |
| Bill of Materials (BOM) | BOM / Bill of Materialslossy | Fully supported | |
| Customer / Account | Third Party (Customer)1:1 | Fully supported | |
| Vendor / Supplier | Third Party (Supplier)1:1 | Fully supported | |
| Sales Order | Order1:1 | Fully supported | |
| Purchase Order | Supplier Order1:1 | Fully supported | |
| Work Order / Manufacturing Order | Project / MRPlossy | Fully supported | |
| Inventory / Stock | Stock1:1 | Mapping required | |
| GL Chart of Accounts | Account (Accounting)1:1 | Fully supported | |
| User / Employee | User1:1 | Fully supported | |
| Custom Objects / User-Defined Fields | Extrafields (extra fields)lossy | Mapping required | |
| Multi-Currency Configuration | Multi-Currency Setuplossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Syscom ERP gotchas
No documented public API for automated data extraction
Modular architecture requires full module inventory before scoping
On-premise deployments require direct database access coordination
Multi-currency setup must be mapped explicitly at migration time
Dolibarr ERP gotchas
Foreign key constraint errors on cross-distribution database restore
SQL injection vulnerabilities in version 9.0.1
Custom fields stored as JSON in extraoptions require field-by-field deserialization
Decimal precision and rounding configuration affects price fields
No native iOS/Android app forces reliance on browser
Pair-specific challenges
Migration approach
Discovery and module inventory
We audit the active Syscom ERP modules in use (Financials, Distribution, Manufacturing, CRM) and inventory all object sets (Items, BOMs, Customers, Vendors, Sales Orders, Purchase Orders, Work Orders, Inventory, GL Accounts, Users, Custom Fields). For on-premise deployments, we coordinate with the customer's IT team to confirm database access method (direct SQL read or CSV export) and to capture the SQL Server connection details. We also confirm the target Dolibarr installation: self-hosted (version, PHP, MySQL/MariaDB version) or cloud-hosted (DoliCloud or other third-party provider). The discovery output is a written migration scope and an extraction plan for each active module.
Data profiling and extraction
We profile the extracted data for duplicates (customer records with multiple addresses, item codes with variants), inconsistent formats (date formats, address structures, currency codes), and missing required fields. Syscom ERP's multi-currency setup is mapped to the destination's currency configuration before extraction. For on-premise database extraction, we run SQL queries against the Syscom ERP database to pull each object set; for cloud deployments or where database access is unavailable, we guide the customer through the built-in CSV export for each module. The extracted data is staged in a secure, customer-owned cloud storage bucket for transformation.
Schema design and Dolibarr module configuration
We design the destination schema in Dolibarr. This includes enabling the required Dolibarr modules (Products, Third Parties, Orders, Proposals, Stock, MRP, Accounting, Projects), configuring the accounting chart of accounts, setting up multi-currency if applicable, and creating custom extrafields to receive Syscom ERP user-defined fields. If the customer uses an existing Dolibarr instance, we review its configuration and identify any conflicts with the incoming data structure before migration begins.
Sandbox migration and reconciliation
We run a full migration into a test Dolibarr instance (a separate test environment or the customer's sandbox) using production-like data volume. The customer reconciles record counts (Products in, Third Parties in, Orders in, Stock in, GL Accounts in) and spot-checks 25-50 records against the Syscom ERP source. Any mapping corrections and schema adjustments happen in this phase before production migration begins. For database extraction scenarios, we also validate that the SQL queries produce complete and accurate output at this stage.
Production migration in dependency order
We run production migration in record-dependency order: GL Accounts (chart of accounts first for accounting integrity), Third Parties (Customers and Vendors), Products (Items and BOMs), Stock (current on-hand balances), Orders (Purchase Orders then Sales Orders), Work Orders (mapped to Projects), Users (mapped to Dolibarr Users with role-to-permission translation), and Custom Fields (extrafields last because they may reference the above). Multi-currency exchange rates load before any currency-denominated transactions. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and inventory handoff
We freeze Syscom ERP writes during cutover and run a final delta migration of any records modified during the migration window. We validate inventory balances (system inventory vs. Dolibarr stock report), GL account trial balance (if accounting data was migrated), and open order status. We deliver a written inventory of Syscom ERP configurations, custom field definitions, and BOM/routing details for the customer's Dolibarr admin to rebuild post-migration. We support a one-week hypercare window where we resolve reconciliation issues. Workflows, automations, and reports do not migrate; these are documented separately for admin rebuild.
Platform deep dives
Syscom ERP
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Syscom ERP and Dolibarr ERP.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Syscom ERP: Not publicly documented.
Data volume sensitivity
Syscom ERP doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Syscom ERP to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your Syscom ERP to Dolibarr ERP migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Syscom ERP
Other ways to arrive at Dolibarr ERP
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.