ERP migration
Field-level mapping, validation, and rollback between Konnect ERP and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
Konnect ERP
Source
Dolibarr ERP
Destination
Compatibility
11 of 12
objects map 1:1 between Konnect ERP and Dolibarr ERP.
Complexity
BStandard
Timeline
4-6 weeks
Overview
Moving from Konnect ERP to Dolibarr is a structural migration driven by the desire to exit a closed, India-region platform for an open-source system with a documented REST API and no per-user licensing. Konnect ERP organizes data across six core domains — Customers, Items, Projects, Employees, Chart of Accounts, and GST-linked transaction records — but does not expose a bulk export endpoint, so migration scoping begins with a live-instance data audit rather than programmatic enumeration. Dolibarr's modular architecture requires explicit module activation before each object type becomes available for import, which we address during schema design. GST E-Invoicing and E-Way Bill records carry HSN and SAC codes that must be cross-referenced against Dolibarr's tax configuration before import; mismatches are escalated to the customer before any data moves. We do not migrate workflows, automations, or custom-built integrations as code; we deliver a written inventory of each for the customer's admin to 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 Konnect 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.
Konnect ERP
Customer
Dolibarr ERP
ThirdParty (Customer)
1:1Konnect ERP Customer records map to Dolibarr ThirdParty with the Customer type flag. We export name, contact details, GSTIN, billing address, shipping address, and outstanding balance. GSTIN maps to a custom extrafield (fk_extrafields) on ThirdParty rather than a native field. Dolibarr requires the Banque module and the Clients module to be activated before third-party import; we confirm activation during Dolibarr setup and flag any missing module before migration begins.
Konnect ERP
Item (Goods)
Dolibarr ERP
Product
1:1Konnect ERP inventory items map to Dolibarr Product records with type=0 (product/stock). We preserve SKU, description, unit of measure (mapped to Dolibarr's unit category system), cost price, and sales price. HSN codes from Konnect ERP migrate as a Product extrafield; Dolibarr does not have a native HSN field. If the source item carries a stock quantity, we migrate warehouse-linked Stock product lines via the Dolibarr Stock module if activated in the destination.
Konnect ERP
Item (Service)
Dolibarr ERP
Product
1:1Konnect ERP service items map to Dolibarr Product records with type=1 (service). The service flag maps to Dolibarr's ProductType field. Description, SAC (Services Accounting Code) as an extrafield, and the last known service price migrate. Service billing cycles (monthly, annual) require manual configuration in Dolibarr's Service module after migration if recurring billing is required.
Konnect ERP
Chart of Accounts
Dolibarr ERP
Account (Plan Comptable)
1:1Konnect ERP COA records map to Dolibarr Bank accounts, cash accounts, customer accounts, supplier accounts, and miscellaneous accounts. We extract the full account code hierarchy and map each code to a Dolibarr account class (classe 1 through 9 corresponding to French-style accounting or the customer's chosen accounting plan). Account codes that have no direct Dolibarr equivalent are flagged in a reconciliation report before import; the customer provides the target account for each unmapped code.
Konnect ERP
Open Invoice (AR)
Dolibarr ERP
Invoice (Customer)
1:1Konnect ERP outstanding customer invoices map to Dolibarr Facture records with type=customer. We migrate invoice number, invoice date, due date, line items referencing the Product lookup (migrated first), tax amounts, and payment status (unpaid/partial/paid). The Customer link resolves to the ThirdParty record migrated first. Paid invoices are migrated as historical records with the paid status flag set; open invoices retain their status for AR follow-up.
Konnect ERP
Open Invoice (AP)
Dolibarr ERP
Invoice (Supplier)
1:1Konnect ERP outstanding supplier invoices map to Dolibarr Facture records with type=supplier. The supplier link resolves to a ThirdParty record of type=supplier migrated first. Line items reference the Product or service records already present. GST tax amounts from Konnect ERP's E-Way Bill records are preserved as extrafield values for tax audit trails.
Konnect ERP
Project
Dolibarr ERP
Project
1:1Konnect ERP Project records map to Dolibarr Project with project_ref, title, description, customer link (ThirdParty), status, and dates. Project budgets and milestone schedules from Konnect ERP migrate as ProjectTask hierarchy records in Dolibarr. If Konnect ERP project billing is tied to a rate card, we migrate the rate card as a ProjectTask line with predefined billing values.
Konnect ERP
Timesheet Entry
Dolibarr ERP
ProjectTaskTime
1:1Konnect ERP timesheet records link an employee to a project and a date range with hours logged. These map to Dolibarr ProjectTaskTime records linked to the matching Project and a user record. Dolibarr requires the Timesheets module and the Project module to both be active. Entries that reference a project or employee not yet migrated are held in a reconciliation queue until parent records are present.
Konnect ERP
Employee
Dolibarr ERP
User + HRM ExtraFields
1:1Konnect ERP Employee records map to Dolibarr User records (for system login) plus HRM-related extrafields (department, designation, date of joining, employment status). We export personal details, department, designation, and effective-dated status. Dolibarr's HRM module must be activated; if it is not, we create User records with the employee fields migrated as extrafields on the User object. Salary and compensation fields require explicit customer instruction before migration as they may fall under data privacy considerations.
Konnect ERP
GST E-Invoice Record
Dolibarr ERP
Invoice (Custom Extrafields)
1:1Konnect ERP E-Invoicing records carry the IRN (Invoice Reference Number), QR code URL, and GSTIN of both parties. We migrate these as invoice extrafields on the corresponding Dolibarr Facture record. The HSN/SAC codes on line items also migrate as line extrafields. Dolibarr has no native GST compliance module; Indian businesses using Dolibarr typically use community modules from the Dolistore or custom-built extensions for GST filing. We flag this gap explicitly and escalate before any GST record import.
Konnect ERP
E-Way Bill Record
Dolibarr ERP
Shipment (Custom Extrafields)
1:1Konnect ERP E-Way Bill records carry the E-Way Bill number, transporter details, vehicle number, and distance. These do not have a native Dolibarr equivalent. We map them as extrafields on a Dolibarr Expedition (shipment) record linked to the corresponding sales invoice. If the Expedition module is not active, we map to a Note attached to the invoice with the E-Way Bill data as structured text.
Konnect ERP
Custom Object
Dolibarr ERP
Custom Object via ExtraFields
lossyKonnect ERP custom objects created within the platform migrate to Dolibarr as standard objects (ThirdParty, Product, Project, etc.) with custom extrafield columns added via Dolibarr's ExtraFields system (llx_extrafields tables). We pre-create the destination extrafields before import, matching the Konnect ERP field name to a Dolibarr column name and type (string, int, float, date, select). The Dolibarr module that hosts each standard object must be activated before its extrafields can be defined.
| Konnect ERP | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Customer | ThirdParty (Customer)1:1 | Fully supported | |
| Item (Goods) | Product1:1 | Fully supported | |
| Item (Service) | Product1:1 | Fully supported | |
| Chart of Accounts | Account (Plan Comptable)1:1 | Mapping required | |
| Open Invoice (AR) | Invoice (Customer)1:1 | Fully supported | |
| Open Invoice (AP) | Invoice (Supplier)1:1 | Fully supported | |
| Project | Project1:1 | Fully supported | |
| Timesheet Entry | ProjectTaskTime1:1 | Fully supported | |
| Employee | User + HRM ExtraFields1:1 | Fully supported | |
| GST E-Invoice Record | Invoice (Custom Extrafields)1:1 | Fully supported | |
| E-Way Bill Record | Shipment (Custom Extrafields)1:1 | Fully supported | |
| Custom Object | Custom Object via ExtraFieldslossy | 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.
Konnect ERP gotchas
No public API means migration scoping is manual
Module availability varies by company configuration
GST transaction records require HSN/SAC remapping
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
Live-instance data audit and module confirmation
We schedule a guided walkthrough of the live Konnect ERP instance with the customer's administrator. We document every active module (CRM, Projects, HRM, etc.), the count of records per module, the existence of GST transaction records, and any custom objects or fields visible in the UI. We also identify which modules are not in use so that we do not attempt to export data that does not exist. This audit produces a written Migration Object Inventory that serves as the basis for the project scope and timeline estimate.
Dolibarr destination setup and module activation
We provision or audit the target Dolibarr instance (self-hosted or DoliCloud) and activate the modules required for each migrating object type. We configure the Chart of Accounts plan, the company information (fiscal year, currency, address), and the extrafield definitions for GSTIN, HSN/SAC codes, and any Konnect ERP custom fields. We validate that the extrafields are correctly typed and visible in the Dolibarr UI before any import data is prepared.
Export extraction and reconciliation
We extract data from Konnect ERP by module using the export mechanism identified during the audit (direct database query or UI-based export). Each module is extracted independently and cross-referenced for relational integrity — Customer IDs on invoices, Project IDs on timesheets, Employee IDs on payroll records. We produce a pre-migration reconciliation report showing record counts per object and any records with broken foreign-key references that require escalation.
Data transformation and tax code remapping
We transform exported records into Dolibarr-compatible flat files (CSV for the native import wizard) or JSON payloads for the REST API. HSN and SAC codes are written to extrafield columns. GSTIN is validated for 15-character format. Account codes are mapped to the Dolibarr account class hierarchy using the account mapping table agreed upon during scoping. The transformation script emits a field-level mapping document showing every source field and its destination equivalent.
Import in dependency order with per-phase reconciliation
We import records into Dolibarr in strict dependency order: ThirdParty records first (Customers and Suppliers), then Products (goods and services), then Chart of Accounts, then Projects, then Employees, then Invoices (supplier and customer), then GST records as extrafield data on invoices, then E-Way Bill records as extrafields on shipments, then Timesheet entries. Each phase produces a row-count reconciliation report comparing records loaded to records submitted. Only after sign-off on each phase does the next phase begin.
Cutover, final validation, and automation inventory handoff
We freeze writes in Konnect ERP during the cutover window, run a final delta migration of any records modified since the last sync, then mark Dolibarr as the system of record. We deliver the complete Migration Object Inventory, the field-level mapping document, and a written list of every Konnect ERP workflow, automation, and E-Way Bill template that requires manual rebuild in Dolibarr (using Dolistore modules or the native workflow system). We support a one-week hypercare window for reconciliation issues. We do not rebuild automations as Dolibarr workflows within the migration scope.
Platform deep dives
Konnect 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 Konnect 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
Konnect ERP: Not applicable.
Data volume sensitivity
Konnect 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 Konnect ERP to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your Konnect 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 Konnect 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.