ERP migration

Migrate from Syscom ERP to Dolibarr ERP

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 logo

Syscom ERP

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

67%

8 of 12

objects map 1:1 between Syscom ERP and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Syscom ERP logo

Syscom ERP

What's pushing teams away

  • Concentrated UK presence — international or multi-country expansion is harder to support than with global vendors like SAP Business One, NetSuite or Dynamics 365 Business Central.
  • Public pricing is not surfaced — buyers must engage Syscom sales to learn per-user and per-module costs, complicating budget comparisons.
  • Public API documentation and developer portal are not surfaced — integrations with non-Syscom systems typically rely on partner-led implementation.
  • Modest press footprint and limited independent review volume (Crozdesk score 55/100) make peer benchmarking harder than for category leaders.
  • Customers outgrowing mid-market complexity may face heavy implementation work to scale into multi-entity consolidation or multi-currency operations that bigger ERPs handle natively.

Choosing

Dolibarr ERP logo

Dolibarr ERP

What's pulling them in

  • Free open-source core with no per-user license fee makes it the lowest-cost entry point for small teams needing ERP and CRM in one package.
  • Self-hosted deployment gives full data ownership and eliminates vendor lock-in, especially attractive to businesses with compliance requirements.
  • Modular architecture means teams enable only the features they use, keeping the interface uncluttered and reducing learning curve.
  • Fast installation with no technical knowledge required — one reviewer set up multiple businesses in minutes using their own hosting.
  • Active community forum and marketplace of third-party add-ons provide support and extension options without mandatory subscription costs.

Object mapping

How Syscom ERP objects map to Dolibarr ERP

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

maps to

Dolibarr ERP

Product

1:1
Fully supported

Syscom 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)

maps to

Dolibarr ERP

BOM / Bill of Materials

lossy
Fully supported

Syscom 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

maps to

Dolibarr ERP

Third Party (Customer)

1:1
Fully supported

Syscom 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

maps to

Dolibarr ERP

Third Party (Supplier)

1:1
Fully supported

Syscom 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

maps to

Dolibarr ERP

Order

1:1
Fully supported

Syscom 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

maps to

Dolibarr ERP

Supplier Order

1:1
Fully supported

Syscom 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

maps to

Dolibarr ERP

Project / MRP

lossy
Fully supported

Syscom 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

maps to

Dolibarr ERP

Stock

1:1
Mapping required

Current 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

maps to

Dolibarr ERP

Account (Accounting)

1:1
Fully supported

Syscom 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

maps to

Dolibarr ERP

User

1:1
Fully supported

Syscom 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

maps to

Dolibarr ERP

Extrafields (extra fields)

lossy
Mapping required

Syscom 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

maps to

Dolibarr ERP

Multi-Currency Setup

lossy
Fully supported

Syscom 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.

Gotchas + challenges

What specifically takes care here

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 logo

Syscom ERP gotchas

High

No documented public API for automated data extraction

Medium

Modular architecture requires full module inventory before scoping

Medium

On-premise deployments require direct database access coordination

Low

Multi-currency setup must be mapped explicitly at migration time

Dolibarr ERP logo

Dolibarr ERP gotchas

High

Foreign key constraint errors on cross-distribution database restore

High

SQL injection vulnerabilities in version 9.0.1

Medium

Custom fields stored as JSON in extraoptions require field-by-field deserialization

Medium

Decimal precision and rounding configuration affects price fields

Low

No native iOS/Android app forces reliance on browser

Pair-specific challenges

  • No documented public API forces database or CSV extraction

    Syscom ERP does not publish a public REST or SOAP API in our research. Before migration scoping, we require the customer to confirm whether a partner API exists and to provide credentials. If no partner API is available, extraction falls to direct SQL Server database read access (coordinated with the customer's DBA and IT team) or manual CSV export from the application's built-in export functions. Database extraction adds coordination steps and timeline; CSV export depends on Syscom ERP's built-in export capabilities for each module, which may not cover all fields. We cannot initiate standard API-based read operations without confirmation of a partner-only or undocumented endpoint.

  • On-premise extraction requires customer IT coordination

    On-premise Syscom ERP deployments host the application on the customer's own infrastructure, meaning database extraction requires the customer's IT team to grant read access to the SQL Server backend or to run a SQL export script on our behalf. Cloud-deployed Syscom ERP customers provide application-level access directly. This distinction affects the extraction method and timeline for each deployment type. We include a database access checklist in every discovery call for Syscom ERP migrations and budget an additional one to two weeks for on-premise database coordination where required.

  • Dolibarr post-update database migration errors

    Dolibarr's update process applies database schema migrations that can fail when a hosting environment's MySQL or MariaDB version is below the required threshold, or when the UTF-8 key length exceeds the database engine limit (max key length 767 bytes on some MySQL 5.5 versions). We verify the Dolibarr hosting environment's MySQL/MariaDB version before installation. If the customer uses a pre-existing Dolibarr instance with update history, we recommend a pre-migration backup and a clean update pass to the latest stable version before data load begins.

  • Inventory transaction history can exceed migration scope

    Migrating every historical stock movement (receipts, issues, adjustments, transfers) from Syscom ERP into Dolibarr's stock movement log can multiply the record count significantly and extend timeline. Dolibarr's stock module is designed around current balances with optional movement history; it is not a full audit trail optimized for large-volume transaction loads. We scope inventory migration to current on-hand balances by default and offer historical transactions as an explicit optional scope with an adjusted timeline and price. Historical transaction data that is not migrated should remain accessible in Syscom ERP (read-only) or an archive for audit purposes.

  • Manufacturing routing and BOM depth may not fully transfer

    Syscom ERP's manufacturing module supports multi-level BOMs, work order routing with operation sequences, and production scheduling. Dolibarr's BOM module handles bill of materials at a single explosion level and does not natively support production routing with work centers and capacity planning. We extract the full manufacturing hierarchy from Syscom ERP and map it to what Dolibarr supports, documenting multi-level relationships and routing details in a manufacturing handoff sheet for the customer's admin. If the customer relies heavily on production scheduling and capacity planning, we flag this as a potential gap before the migration begins.

Migration approach

Six steps for a successful Syscom ERP to Dolibarr ERP data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Syscom ERP logo

Syscom ERP

Source

Strengths

  • Modular architecture lets manufacturers and distributors pay only for modules they use, reducing total cost.
  • Multi-currency support accommodates international trade and multi-entity operations without a separate currency add-on.
  • On-premise and cloud deployment options give customers flexibility on data residency and infrastructure control.
  • 40+ years of Syscom PLC market presence indicates stability and long-term support commitment.
  • Industry-specific variants like ApparelX indicate vertical depth for apparel-sector customers.

Weaknesses

  • No publicly documented API or developer portal found in our research, limiting automated migration tooling access.
  • Modular pricing model means total cost is opaque until a full module inventory is completed.
  • No public review dataset found on G2, Capterra, or TrustRadius, making independent quality assessment difficult.
  • Smaller company size ($8.5M revenue) relative to major ERP vendors raises questions about long-term R&D investment and support capacity.
  • No published SLA or uptime guarantees found, which is a concern for cloud-deployed customers.
Dolibarr ERP logo

Dolibarr ERP

Destination

Strengths

  • Free core software with AGPL license and no per-user mandatory fee for self-hosted deployments.
  • Modular architecture lets teams activate only needed features, keeping the interface focused and the database lean.
  • Self-hosted option provides full data sovereignty and avoids recurring SaaS subscription costs.
  • Built-in CSV/Excel import and export wizard with saved profiles simplifies recurring data operations.
  • Low-code Module Builder allows functional extensions without writing PHP code.

Weaknesses

  • No native documented REST API for programmatic bulk operations — all migrations depend on the import/export wizard or direct database access.
  • Reporting and analytics are weak without paid add-ons, and built-in charts are limited compared to modern SaaS platforms.
  • UI design is described as dated by multiple reviewers, with infrequent visual updates to the default theme.
  • Community-only support for self-hosted deployments means no SLA or guaranteed response time for issues.
  • Security vulnerabilities (CVE-2024-5314, CVE-2024-5315) in version 9.0.1 with no immediate patch reported.

Complexity grading

How hard is this migration?

Standard ERP migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Syscom ERP and Dolibarr ERP.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Syscom ERP: Not publicly documented.

  • Data volume sensitivity

    B

    Syscom ERP doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Syscom ERP to Dolibarr ERP migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Syscom ERP to Dolibarr ERP data migrations

Answers to the questions buyers ask most during Syscom ERP to Dolibarr ERP migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Migrations land between three and five weeks for single-module deployments under 10,000 items and 2,000 customers with no manufacturing data. Migrations with multi-level BOMs, Work Orders, multi-currency ledgers, bin-level inventory detail, or requiring direct SQL Server database extraction coordination extend to eight to twelve weeks. The extraction method (direct database access vs. CSV export) is the primary timeline variable because it affects how many manual steps the customer must perform before transformation begins.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Syscom ERP.
Land in Dolibarr ERP, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day