ERP migration

Migrate from iGEO ERP to Dolibarr ERP

Field-level mapping, validation, and rollback between iGEO ERP and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.

iGEO ERP logo

iGEO ERP

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

92%

11 of 12

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

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from iGEO ERP to Dolibarr is a shift from a vertically specialized, pricing-tier-gated field-service platform to an open-source modular ERP-CRM that runs on-premises or in the cloud. iGEO structures its data around Clients, Contracts, Work Orders, Routes, Technicians, Services, Suppliers, Stock, and Invoices, with pesticide-tracking and compliance fields native to the installation. Dolibarr uses a modular architecture where you activate only the modules you need: third-party, product, stock, invoicing, contract, project, and others. We extract the full company export file from iGEO, partition it by object, and sequence each into Dolibarr in dependency order. Pest-control compliance fields and pesticide codes require explicit field-level mapping because they vary by country and customer configuration. Dolibarr has no native routing or AI route-planning module; we document any route-assignment data as notes on the migrated Work Orders and flag this gap for the customer's admin. Workflows, automations, and iGEO's AI route planning do not migrate; we deliver a written inventory of these for rebuild in Dolibarr.

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

iGEO ERP logo

iGEO ERP

What's pushing teams away

  • Limited accounting module depth — multiple reviews note the platform lacks sufficient accounting and financial reporting features, forcing teams to maintain a separate finance tool.
  • Sparse public documentation and API spec — there is no publicly documented developer portal, community forum, or Swagger spec, making self-service integration and troubleshooting difficult.
  • Custom pricing required for enterprise features — API access and advanced modules are gated behind Custom tier plans, creating cost uncertainty for growing companies evaluating exit.
  • Pest control and compliance-specific configuration can become rigid — industry-specific fields, pesticide codes, and regulatory statuses vary by country and can be hard to migrate cleanly to a different vertical CRM.

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 iGEO ERP objects map to Dolibarr ERP

Each row shows how a iGEO 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.

iGEO ERP

Client

maps to

Dolibarr ERP

ThirdParty (ThirdParty module)

1:1
Fully supported

iGEO Client records hold contact details, service locations, and associated contracts. We map them to Dolibarr ThirdParty, preserving the primary address, any secondary service locations as additional contact records within the ThirdParty, and the client code as ref_client. Multi-location clients from iGEO become multiple Dolibarr contact addresses under a single ThirdParty rather than separate records, which avoids the orphaned-location problem common in iGEO exports.

iGEO ERP

Contract

maps to

Dolibarr ERP

Contract (Contrat module)

1:1
Fully supported

iGEO Contracts define service agreements with scope, frequency, pricing, and work-order templates. We migrate contract headers and line items, mapping frequency patterns (weekly, monthly, quarterly) to Dolibarr Contrat frequency fields and service codes to Dolibarr product references. Contracts are migrated before Work Orders to satisfy the parent-record dependency so that child work orders can reference the correct contract ID during load.

iGEO ERP

Service Type

maps to

Dolibarr ERP

Product (Product module)

1:1
Fully supported

iGEO Service Types represent the catalog of offerings — insect treatment, rodent control, water quality inspection, and others. We map them to Dolibarr Product records with type=service. The iGEO service type code becomes the Product ref, and the description maps to the Product label. Pesticide-related service types receive a custom extrafield to flag regulatory classification that the customer's admin configures post-migration.

iGEO ERP

Work Order

maps to

Dolibarr ERP

Intervention (Interventions module)

1:1
Fully supported

iGEO Work Orders are the operational core — each ties a Client, a Service Type, a Technician, a scheduled date, a status, and a location. We migrate all open and historical Work Orders to Dolibarr Intervention records. The iGEO technician assignment maps to the Intervention user field. The client and service references resolve to ThirdParty and Product lookups that we pre-create during the Client and Service mapping phases.

iGEO ERP

Route

maps to

Dolibarr ERP

Agenda / Event (Agenda module)

1:1
Fully supported

iGEO Routes are daily technician schedules generated by AI route planning. Dolibarr has no native AI routing module — this is a known functional gap. We extract route assignments including visit sequence, estimated times, and geographic waypoints, and map them to Dolibarr Agenda events with an Intervention link. Route ordering and day-of-week scheduling are preserved as Agenda event timestamps. The customer should evaluate Dolistore routing addons if automated route optimization is required post-migration.

iGEO ERP

Technician

maps to

Dolibarr ERP

User (HRM module)

1:1
Fully supported

iGEO Technician records include contact details, assigned territories, availability, and mobile app credentials. We map them to Dolibarr User records, preserving territory assignments as a custom extrafield. User credentials for mobile app access do not migrate — the customer provisions new Dolibarr mobile access credentials post-migration. Inactive technicians are migrated as inactive User records to preserve historical assignment on Work Orders.

iGEO ERP

Supplier

maps to

Dolibarr ERP

ThirdParty (ThirdParty module with supplier flag)

1:1
Fully supported

iGEO Supplier records hold vendor contact details and associated product or service offerings. We map them to Dolibarr ThirdParty with the Supplier flag enabled. Associated product offerings migrate as Dolibarr Product records linked to the supplier. Supplier contact details preserve during import.

iGEO ERP

Stock

maps to

Dolibarr ERP

Stock (Stock module)

1:1
Fully supported

iGEO Stock entries track inventory items, quantities, reorder points, and supplier associations. We migrate stock records including current quantities and reorder thresholds, mapping units of measure to Dolibarr Warehouse stock entries. Stock locations in iGEO map to Dolibarr Warehouses. If iGEO tracks pesticide or chemical inventory with regulatory compliance codes, we map those to Dolibarr extrafields and flag them for the customer to configure against local regulations.

iGEO ERP

Invoice

maps to

Dolibarr ERP

Invoice / Bill (Invoicing module)

1:1
Fully supported

iGEO Invoice records include line items, taxes, totals, and payment status. We migrate invoice headers and line items, preserving regulatory compliance codes and pesticide tracking fields that may appear on invoice records. Tax rates are mapped to Dolibarr's VAT or tax rules by country. Invoice status (paid, unpaid, cancelled) migrates to Dolibarr payment status fields. Historical invoices are imported with validated status to prevent re-validation attempts during migration.

iGEO ERP

Quote / Estimate

maps to

Dolibarr ERP

Proposal / Commercial Proposal (Commercial module)

1:1
Fully supported

iGEO Quotes and estimates are proposals sent to clients before service commitment. We migrate these records including line items, totals, and status (sent, accepted, rejected), mapping them to Dolibarr Commercial Proposal records. Status values are mapped to Dolibarr's draft, open, signed, and refused commercial proposal statuses.

iGEO ERP

Custom Field

maps to

Dolibarr ERP

Extrafield (Extrafields system)

lossy
Fully supported

iGEO custom fields are industry-specific compliance and pesticide-tracking fields configured per installation. We document every custom field definition during discovery, mapping SQL-level extrafields in Dolibarr to match iGEO field types (text, integer, select, date, checkbox). Compliance-relevant extrafields are documented separately with regulatory context for the customer to validate against local pest control regulations before go-live.

iGEO ERP

Employee

maps to

Dolibarr ERP

User (HRM module)

1:1
Fully supported

iGEO Employee records include staff beyond field technicians — office staff, admins, and managers. We migrate these as Dolibarr User records, preserving role assignments and department associations as extrafields. User status (active/inactive) is preserved during migration.

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.

iGEO ERP logo

iGEO ERP gotchas

High

API access is tier-gated and not publicly documented

Medium

File export dumps the entire company dataset at once

Medium

Industry-specific service types and compliance fields vary by installation

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

  • iGEO file export dumps the entire dataset at once

    iGEO's export feature generates a single comprehensive file of all company data rather than selective object exports. We scope exactly which objects are relevant before triggering the export, coordinate with the customer to avoid pulling unnecessary records, and partition the export file into migration-ready chunks aligned to our sequencing plan. If API access is available on the customer's plan tier, we prefer API extraction for selective object retrieval. If API is not available (Base plan), we rely on file export and filter accordingly during the transform phase before loading Dolibarr.

  • Dolibarr has no native AI route planning module

    iGEO's AI-powered route planning generates optimized daily technician routes automatically. Dolibarr has no equivalent native module — scheduling is managed through the Agenda module manually or via a Dolistore addon. We extract route assignments from iGEO and map them to Dolibarr Agenda events as a one-time historical record, but we cannot reproduce the AI optimization logic. The customer's admin should evaluate Dolistore scheduling addons or a third-party routing tool if automated route planning is required post-migration.

  • Industry-specific compliance fields vary by iGEO installation

    iGEO is configured differently per vertical — pest control, water quality, HVAC, pool care. Service type codes, pesticide tracking fields, and regulatory compliance statuses are specific to the customer's country and operational scope. During discovery we document the customer's exact iGEO configuration and adapt field mappings for each compliance-relevant object. The customer must validate migrated compliance fields against local regulatory requirements before go-live because Dolibarr's extrafields system requires manual configuration for jurisdiction-specific rules.

  • Dolibarr invoice validation requires folder rename permission

    Dolibarr validates invoices by renaming temporary document folders, which can fail if the web server lacks write permission on the documents directory. During migration, we coordinate with the customer's Dolibarr hosting provider to verify permissions before importing validated invoices. This is a known Dolibarr troubleshooting scenario documented on the Dolibarr wiki, and we address it as part of the migration readiness checklist before the invoice phase begins.

  • Database key length limits can affect migrations on older MariaDB versions

    Dolibarr GitHub issue #16315 documents a DB_ERROR_1071 when upgrading or migrating on MariaDB versions below 10.3 with certain index definitions exceeding the 767-byte key length. If the customer's Dolibarr instance runs on a legacy database version, we flag this during the hosting readiness check and recommend upgrading the MariaDB instance before migration. This does not affect the iGEO source side but can block imports into Dolibarr if the destination database version is outdated.

Migration approach

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

  1. Discovery and export method confirmation

    We audit the source iGEO configuration across plan tier (Base or Custom), enabled modules, object record counts, custom field definitions, and pesticide/compliance field usage. We confirm whether API access is available on the customer's plan tier for selective extraction, or whether we are relying on the full file export. We document the iGEO installation's specific vertical configuration (pest control, environmental health, or mixed) to scope compliance-field mapping scope. The discovery output is a written migration scope, record-count estimate, and export method confirmation.

  2. Dolibarr module selection and destination schema setup

    We configure the Dolibarr destination instance by activating the required modules: third-party, product, stock, invoicing, contract, intervention (for Work Orders), agenda, and HRM. We pre-create all custom extrafields matching iGEO custom field definitions, including compliance and pesticide tracking fields. We configure warehouse locations matching iGEO stock locations, tax rules matching the customer's jurisdiction, and product service codes matching iGEO service type codes. The Dolibarr schema is validated in a test environment before any data moves.

  3. File extraction and object partitioning

    We trigger the iGEO full-file export (or run API extraction if Custom tier is confirmed), receive the export file, and partition it into object-specific chunks aligned to the migration sequence. We apply a filter pass to remove test records, duplicate entries, and any data outside the agreed migration scope. Each partition is validated against the record counts from discovery before the transform phase begins.

  4. Data transformation and field-level mapping

    We transform each object partition using the documented field mappings. Client records receive ThirdParty IDs that become the lookup targets for all dependent objects. Service type codes receive Product IDs before Work Order migration. Contract IDs are resolved before Intervention records reference them. Tax rates are mapped to Dolibarr's jurisdiction-specific VAT rules. Compliance and pesticide fields receive custom extrafield values that are flagged for the customer to validate against local regulations post-migration.

  5. Migration in dependency order with reconciliation

    We load migrated data into Dolibarr in dependency order: ThirdParties (Clients and Suppliers first), Products (Service Types), Contracts, Users (Technicians and Employees), Stock, Interventions (Work Orders with technician and contract lookups resolved), Agenda events (Routes), Invoices, and Commercial Proposals. Each phase emits a row-count reconciliation report. Route assignments are loaded as Agenda events with an Intervention link. The customer spot-checks migrated records during a review window before the next phase begins.

  6. Cutover, validation, and automation inventory handoff

    We freeze iGEO writes during cutover, run a final delta migration of any records modified during the migration window, then enable Dolibarr as the system of record. We deliver a written inventory of iGEO workflows, route-planning rules, and automated scheduling logic for the customer's admin to rebuild in Dolibarr using the Agenda and Project modules or a Dolistore addon. We do not rebuild automations as Dolibarr configuration inside the migration scope. We support a one-week post-cutover window for reconciliation issues raised by the customer's team.

Platform deep dives

Context on both ends of the pair

iGEO ERP logo

iGEO ERP

Source

Strengths

  • Unified platform covering CRM, scheduling, routing, invoicing, and warehouse for field service teams
  • Mobile-first design with signature capture lets technicians close work orders in the field without returning to the office
  • AI-driven route planning reduces manual dispatch effort and optimizes technician daily travel
  • Specialized pest control compliance features including pesticide usage tracking and service activity logging are native
  • Multi-language support (EN, FR, IT, PT, ES) serves companies operating across European markets

Weaknesses

  • Accounting module is shallow — users report needing a separate finance tool to cover full bookkeeping needs
  • API access is gated behind Custom pricing tier with no publicly documented endpoint spec or developer portal
  • Limited transparent pricing information — no published per-user or per-module cost breakdown on the vendor site
  • Custom compliance fields and industry-specific configurations can create rigidity when migrating to a different vertical CRM
  • Integration ecosystem is narrow — only Azure, Google, Sage 200, and SAP Agile Data Preparation are explicitly listed
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. All 8 core objects map 1:1 between iGEO ERP and Dolibarr ERP.

B

Overall complexity

Standard migration

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

  • Object compatibility

    A

    All 8 core objects map 1:1 between iGEO ERP and Dolibarr ERP.

  • 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

    iGEO ERP: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your iGEO 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 iGEO ERP to Dolibarr ERP data migrations

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

Can't find your answer?

Walk through your iGEO ERP to Dolibarr ERP migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations land between three and five weeks for accounts under 15,000 Clients, 5,000 Work Orders, and 2,000 Invoices with no complex compliance field configuration. Migrations with full historical work-order and route-assignment records, multi-country tax configurations, pesticide compliance fields requiring jurisdiction-specific validation, or supplier-stock data move to six to ten weeks because of field-level compliance mapping and Dolibarr module configuration time.

Adjacent paths

Related migrations to explore

Ready when you are

Move from iGEO 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