ERP migration
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
Source
Dolibarr ERP
Destination
Compatibility
11 of 12
objects map 1:1 between iGEO ERP and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
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 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
Dolibarr ERP
ThirdParty (ThirdParty module)
1:1iGEO 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
Dolibarr ERP
Contract (Contrat module)
1:1iGEO 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
Dolibarr ERP
Product (Product module)
1:1iGEO 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
Dolibarr ERP
Intervention (Interventions module)
1:1iGEO 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
Dolibarr ERP
Agenda / Event (Agenda module)
1:1iGEO 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
Dolibarr ERP
User (HRM module)
1:1iGEO 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
Dolibarr ERP
ThirdParty (ThirdParty module with supplier flag)
1:1iGEO 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
Dolibarr ERP
Stock (Stock module)
1:1iGEO 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
Dolibarr ERP
Invoice / Bill (Invoicing module)
1:1iGEO 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
Dolibarr ERP
Proposal / Commercial Proposal (Commercial module)
1:1iGEO 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
Dolibarr ERP
Extrafield (Extrafields system)
lossyiGEO 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
Dolibarr ERP
User (HRM module)
1:1iGEO 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.
| iGEO ERP | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Client | ThirdParty (ThirdParty module)1:1 | Fully supported | |
| Contract | Contract (Contrat module)1:1 | Fully supported | |
| Service Type | Product (Product module)1:1 | Fully supported | |
| Work Order | Intervention (Interventions module)1:1 | Fully supported | |
| Route | Agenda / Event (Agenda module)1:1 | Fully supported | |
| Technician | User (HRM module)1:1 | Fully supported | |
| Supplier | ThirdParty (ThirdParty module with supplier flag)1:1 | Fully supported | |
| Stock | Stock (Stock module)1:1 | Fully supported | |
| Invoice | Invoice / Bill (Invoicing module)1:1 | Fully supported | |
| Quote / Estimate | Proposal / Commercial Proposal (Commercial module)1:1 | Fully supported | |
| Custom Field | Extrafield (Extrafields system)lossy | Fully supported | |
| Employee | User (HRM module)1:1 | 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.
iGEO ERP gotchas
API access is tier-gated and not publicly documented
File export dumps the entire company dataset at once
Industry-specific service types and compliance fields vary by installation
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 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.
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.
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.
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.
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.
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
iGEO ERP
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. All 8 core objects map 1:1 between iGEO ERP and Dolibarr ERP.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across iGEO ERP and Dolibarr ERP.
Object compatibility
All 8 core objects map 1:1 between iGEO ERP and Dolibarr ERP.
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
iGEO ERP: Not publicly documented.
Data volume sensitivity
iGEO 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 iGEO ERP to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave iGEO 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.