ERP migration
Field-level mapping, validation, and rollback between Runple and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
Runple
Source
Dolibarr ERP
Destination
Compatibility
9 of 12
objects map 1:1 between Runple and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Runple to Dolibarr is a structural migration for Austrian and German-speaking European businesses that have outgrown Runple's performance constraints and opaque pricing (reported at €4,990 per month for inventory management) in favor of Dolibarr's community-driven, open-source model. Runple's limited API documentation means we extract data through negotiated data dumps or CSV exports rather than authenticated API calls, then load through Dolibarr's CSV import wizard or direct database import. EU VAT compliance codes and reverse-charge rules stored in Runple's tax configuration require manual remapping in Dolibarr before go-live. Dolibarr's modular architecture lets you activate only the accounting, inventory, and CRM modules your business needs, reducing operational complexity compared to Runple's consolidated model. We deliver a written handoff of Runple workflows and configurations that your admin rebuilds in Dolibarr's module settings post-migration.
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 Runple 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.
Runple
Customer
Dolibarr ERP
ThirdParty (Contact / ThirdParty)
1:1Runple customer records map to Dolibarr ThirdParty objects in customer mode. We extract name, address, tax identification number, and payment terms, then import via Dolibarr's CSV import wizard or direct MySQL insert. The dedupe key is the customer email or tax ID. EU VAT codes stored in Runple's tax fields map to Dolibarr's local tax configuration (Tva Intra and Code client) and require manual verification in Dolibarr's ThirdParty settings before go-live.
Runple
Supplier
Dolibarr ERP
ThirdParty (Supplier mode)
1:1Runple supplier records map to Dolibarr ThirdParty objects toggled to supplier mode. Supplier-specific fields including payment terms and bank details migrate to Dolibarr's Bank Account and Fournisseurisseur (Supplier) tabs. We resolve supplier references on Purchase Orders and incoming invoices after both the supplier and the purchase transaction records are loaded.
Runple
Product / Item
Dolibarr ERP
Product
1:1Runple product catalog entries (SKU, name, description, unit price, cost, stock quantity) map directly to Dolibarr Product records. We import via Dolibarr's product CSV import profile, preserving Runple's stock levels as initial warehouse quantities. Multi-warehouse stock configurations in Runple map to Dolibarr's Warehouse objects with stock movement history loaded as separate StockMovement records per warehouse.
Runple
Invoice (Sales)
Dolibarr ERP
Facture (Invoice)
1:1Runple sales invoices map to Dolibarr Facture records. We extract invoice number, issue date, due date, customer reference, line items (product, quantity, unit price, VAT rate), totals, and payment status. Historical invoices (paid, open, overdue) migrate with their status preserved. Invoice PDFs stored in Runple's document folder migrate as file attachments on the corresponding Dolibarr Facture records.
Runple
Payment
Dolibarr ERP
Paiement (Payment)
1:1Runple payment records (linked to invoices, amounts, dates, methods) map to Dolibarr Paiement records. We resolve the link back to the migrated Facture record by invoice number match so that Dolibarr's Accounts Receivable aging reflects correctly. Partial payments are supported by mapping Runple's split payment records to individual Paiement entries referencing the same Facture.
Runple
Open AR / AP
Dolibarr ERP
Facture (open) and Paiement
1:1Outstanding receivables and payables require aging bucket preservation. We extract current open invoice balances with due dates and load them as Dolibarr Facture records with status set to Unpaid (unpaid status). The payment reconciliation (reconciling payments against open invoices) occurs in Dolibarr's Bank Reconciliation module after migration, guided by a reconciliation spreadsheet we deliver alongside the migration.
Runple
Stock / Inventory
Dolibarr ERP
Product + Stock
1:1Runple stock levels per product per warehouse map to Dolibarr Product records with current stock quantities per Warehouse. Stock movement history (inbound, outbound, adjustment) loads as Dolibarr StockMovement records with movement type, quantity, date, and warehouse reference. We batch movements by month to avoid overwhelming Dolibarr's stock report if the history spans multiple years.
Runple
Chart of Accounts
Dolibarr ERP
Accountancy Account
1:1Runple's chart of accounts entries map to Dolibarr's Accountancy Account objects. We extract account code, label, and type (asset, liability, equity, revenue, expense) and load them through Dolibarr's accounting module CSV import. Account groups and cost centre hierarchies from Runple map to Dolibarr's category structure if the accounting module is enabled.
Runple
User and Role
Dolibarr ERP
User + Permission
1:1Runple user accounts with role assignments require remapping to Dolibarr's permission system. We extract user email, name, and role flags and load them as Dolibarr User records. Role permissions (read/write/admin flags per module) map to Dolibarr's module-level permission grants which the customer's admin verifies and adjusts post-migration because Dolibarr's permission model operates at the module and feature level rather than per-object.
Runple
Working Time Records
Dolibarr ERP
Holiday / Task (if enabled)
lossyRunple time tracking records (hours, dates, employee assignments) have no direct Dolibarr equivalent unless the Holiday or Project/Task module is activated. We map time entries to Dolibarr Task records under a Project named 'Migrated Time Records' and flag the mapping in the scope document. If the customer activates Dolibarr's HR module, we remap to the equivalent Holiday object type.
Runple
Commission and Salary Records
Dolibarr ERP
Custom fields or Note
lossyRunple stores commission and salary data as HR-adjacent records with no native Dolibarr equivalent in the core accounting module. We extract these as a structured CSV and deliver them alongside the migration. The customer's admin chooses to load them as custom fields on the User or ThirdParty object, or as a linked spreadsheet reference in a Note. This is a configuration decision made during scoping.
Runple
VAT / Tax Codes
Dolibarr ERP
Tax / VAT Configuration
lossyRunple's EU VAT compliance codes and reverse-charge rules require manual remapping in Dolibarr's Tax and VAT settings. We extract Runple's tax code table (rate, type, jurisdiction) and deliver it as a reference spreadsheet alongside the migration. The customer's admin creates matching Dolibarr Tax models (Taux de TVA, TaxES, Reverse Charge) and validates that invoice totals recalculate correctly before go-live.
| Runple | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Customer | ThirdParty (Contact / ThirdParty)1:1 | Fully supported | |
| Supplier | ThirdParty (Supplier mode)1:1 | Fully supported | |
| Product / Item | Product1:1 | Fully supported | |
| Invoice (Sales) | Facture (Invoice)1:1 | Fully supported | |
| Payment | Paiement (Payment)1:1 | Fully supported | |
| Open AR / AP | Facture (open) and Paiement1:1 | Fully supported | |
| Stock / Inventory | Product + Stock1:1 | Fully supported | |
| Chart of Accounts | Accountancy Account1:1 | Fully supported | |
| User and Role | User + Permission1:1 | Fully supported | |
| Working Time Records | Holiday / Task (if enabled)lossy | Mapping required | |
| Commission and Salary Records | Custom fields or Notelossy | Mapping required | |
| VAT / Tax Codes | Tax / VAT Configurationlossy | 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.
Runple gotchas
Premium pricing tiers are not publicly documented
Limited public API documentation restricts migration scripting
Performance degrades under heavy transactional load
German-language interface and EU-specific features may not map to non-EU destination systems
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 extraction scoping
We audit the Runple account for accessible export methods: CSV export availability by module (Customers, Products, Invoices, Stock), negotiated data dump request through the customer's account manager, and any available API endpoints on the current plan. We document the current record counts, date ranges of historical data to migrate, and any EU VAT or tax code configurations that require remapping. The discovery output is a written extraction plan specifying data format (CSV vs SQL dump), chunking strategy for large tables, and a timeline for the account manager data dump request if the public export is insufficient.
Destination Dolibarr setup and module activation
We review the target Dolibarr installation (self-hosted or DoliCloud) and activate the modules required by the migration scope: ThirdParty (for customer and supplier contacts), Product (for product catalog), Facture (for invoices), Stock (for inventory), and the Accountancy module if chart of accounts migration is required. We verify the Dolibarr version and run the /install/ schema upgrade step if the version is older than the data being imported. We configure the necessary Tax and VAT models in Dolibarr using the extracted Runple tax code table as reference, pending the customer's admin verification.
Data extraction and CSV preparation
We run data extraction from Runple via CSV export (chunked by year for large tables) or via the negotiated data dump from the account manager. We transform the exported data into Dolibarr-compatible CSV format, mapping Runple field names to Dolibarr import profile column headers. We apply encoding normalization (UTF-8, consistent date formats) and split multi-record types (line items, stock movements) into separate normalized files aligned with Dolibarr's import wizard expectations. The transformation output is a staged set of CSVs ready for Dolibarr import with a reconciliation count sheet showing expected record counts per object.
Staged import and reconciliation
We run staged imports into the destination Dolibarr instance in dependency order: ThirdParty records (Customers and Suppliers, using tax ID or email as dedupe key), then Products with initial stock levels, then Facture records (oldest first), then Payments linked back to Factures by invoice number, then Stock movement history, then Users and Permissions, and finally any time or HR records if scoped. After each import batch, we reconcile the row count against the source extraction count sheet and spot-check five to ten records visually against the Runple source. Errors are corrected in the staging CSV and re-imported before proceeding to the next batch.
VAT and tax configuration handoff
We deliver a structured tax code reference document mapping each Runple VAT rate and reverse-charge rule to its equivalent Dolibarr Tax model. The customer's admin creates the matching Tax, Taux de TVA, and Reverse Charge configurations in Dolibarr's setup module, validates that a sample invoice recalculates correctly with the new tax codes applied, and signs off on the tax configuration before the AR/AP reconciliation step. We do not configure tax codes directly because EU VAT compliance is a regulatory responsibility that belongs with the customer's finance team.
Cutover, AR/AP reconciliation, and go-live support
We freeze Runple write access during cutover, run a final delta migration of any records modified during the migration window, and enable Dolibarr as the system of record. We deliver a reconciliation summary showing total records migrated per object and any records flagged as partial (missing fields) or unlinked (orphan references). We deliver a written workflow and configuration inventory document listing every Runple automation or setting that requires manual rebuild in Dolibarr's module settings. We support a five-business-day hypercare window for reconciliation issues raised by the customer's team.
Platform deep dives
Runple
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. All 8 core objects map 1:1 between Runple and Dolibarr ERP.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Runple and Dolibarr ERP.
Object compatibility
All 8 core objects map 1:1 between Runple 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
Runple: Not publicly documented.
Data volume sensitivity
Runple 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 Runple to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your Runple 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 Runple
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.