ERP migration

Migrate from Runple to Dolibarr ERP

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

Runple logo

Runple

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

75%

9 of 12

objects map 1:1 between Runple and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Runple logo

Runple

What's pushing teams away

  • Performance degrades under extensive data load, with slow responses reported as operations scale.
  • Limited customer base of 200+ suggests less real-world stress testing compared to established ERP vendors.
  • Reporting depth reported as insufficient for businesses requiring granular financial analysis.
  • Smaller vendor with 16 team members raises concerns about long-term support and feature development capacity.
  • Documentation and community resources are thin, making self-service troubleshooting difficult.

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

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

maps to

Dolibarr ERP

ThirdParty (Contact / ThirdParty)

1:1
Fully supported

Runple 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

maps to

Dolibarr ERP

ThirdParty (Supplier mode)

1:1
Fully supported

Runple 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

maps to

Dolibarr ERP

Product

1:1
Fully supported

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

maps to

Dolibarr ERP

Facture (Invoice)

1:1
Fully supported

Runple 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

maps to

Dolibarr ERP

Paiement (Payment)

1:1
Fully supported

Runple 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

maps to

Dolibarr ERP

Facture (open) and Paiement

1:1
Fully supported

Outstanding 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

maps to

Dolibarr ERP

Product + Stock

1:1
Fully supported

Runple 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

maps to

Dolibarr ERP

Accountancy Account

1:1
Fully supported

Runple'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

maps to

Dolibarr ERP

User + Permission

1:1
Fully supported

Runple 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

maps to

Dolibarr ERP

Holiday / Task (if enabled)

lossy
Mapping required

Runple 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

maps to

Dolibarr ERP

Custom fields or Note

lossy
Mapping required

Runple 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

maps to

Dolibarr ERP

Tax / VAT Configuration

lossy
Fully supported

Runple'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.

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.

Runple logo

Runple gotchas

High

Premium pricing tiers are not publicly documented

Medium

Limited public API documentation restricts migration scripting

Medium

Performance degrades under heavy transactional load

Low

German-language interface and EU-specific features may not map to non-EU destination systems

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

  • Runple extraction requires negotiated data access rather than API calls

    Runple's public API documentation is not publicly available, and our research found no authenticated API reference or developer endpoint documentation. This means we cannot build an automated API extraction for Runple. During scoping, we request a structured data dump negotiated directly with the customer's Runple account manager, or we extract via Runple's CSV export where that feature is accessible on the customer's plan. Large export batches (10,000+ rows) can time out or run slowly because of Runple's reported performance degradation under load, so we chunk large exports into monthly batches and request them during off-peak hours. Without a complete data dump agreement in place before migration begins, extraction scope cannot be confirmed.

  • EU VAT codes stored in Runple require manual remapping in Dolibarr

    Runple is built for Austrian and German-speaking European markets, with EU VAT handling, reverse-charge rules, and Austrian tax authority codes baked into its tax configuration. Dolibarr ships with standard EU VAT rate configurations but does not include Austrian or German-specific tax authority codes out of the box. We extract Runple's tax code table and deliver it as a reference document, but the customer's admin must create matching Dolibarr Tax models (Taux de TVA, TaxES, Reverse Charge Type) and validate invoice totals recalculate correctly before go-live. Migrations that skip this step produce invoices with incorrect VAT calculations in production.

  • Dolibarr's version upgrade path is sequential; skipping versions causes schema errors

    If the destination Dolibarr instance is running a newer major version than the source data export, direct database import can fail with schema mismatch errors. The Dolibarr community forum documents cases where restoring a backup from an older version to a newer installation requires running the Dolibarr installer at /install/ to apply sequential schema upgrades. We verify the Dolibarr version on the destination instance before migration begins and ensure the installer is run if the version delta is greater than one major release. This prevents the DB_ERROR_1071 key length and similar schema errors documented in Dolibarr's GitHub issue tracker.

  • Runple performance slowdowns affect export generation timelines

    Runple's performance degrades under extensive data loads, which directly affects how quickly large CSV exports generate. We chunk large exports by year or by record type to reduce the load per request and schedule them during off-peak hours to avoid timeouts. If Runple's export generation fails repeatedly, we escalate to a negotiated full data dump with the customer's account manager as the fallback extraction path. This can extend the extraction phase by one to two weeks beyond initial scoping estimates.

  • Dolibarr's CSV import wizard processes one table at a time with no batch rollback

    Dolibarr's native import module processes flat files one object type at a time (Customers, then Products, then Invoices, etc.) and does not support transactional rollback across imports. If a later import batch introduces errors, correcting it requires manual re-import or direct database update rather than a single undo. We validate each CSV batch against Dolibarr's field requirements before import, run a reconciliation count after each batch, and keep raw CSV files for reference. This is not a migration blocker but increases the post-import validation workload.

Migration approach

Six steps for a successful Runple to Dolibarr ERP data migration

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

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

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

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

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

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

Context on both ends of the pair

Runple logo

Runple

Source

Strengths

  • Combines accounting, inventory, POS, and e-commerce in a single subscription rather than separate tools.
  • 14-day free trial with no credit card requirement lowers the evaluation barrier for small businesses.
  • AI-powered features aim to reduce manual accounting work for non-finance users.
  • German-language and EU-compliant VAT handling makes it suitable for Austrian and German-speaking European businesses.
  • Built-in dashboards provide real-time revenue, margin, and expense visibility without third-party reporting tools.

Weaknesses

  • Small customer base of 200+ indicates limited adoption and less third-party ecosystem support.
  • Performance issues reported under extensive data loads make it less suitable for high-volume operations.
  • Thin documentation and small team raise concerns about long-term vendor stability and support responsiveness.
  • Limited API documentation publicly available, making integrations and data extraction harder to plan.
  • Pricing appears positioned at the premium end (€4990/month for inventory management) for a small-business tool.
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 Runple and Dolibarr ERP.

B

Overall complexity

Standard migration

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

  • Object compatibility

    A

    All 8 core objects map 1:1 between Runple 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

    Runple: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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 consultation

Migrations land between three and five weeks for accounts under 10,000 invoices, 2,000 customers, and 5,000 products where Runple's CSV export is accessible without account manager escalation. Migrations with large transactional histories (50,000+ invoices), multi-warehouse stock movement records, chart of accounts restructuring, or EU VAT code remapping scope move to eight to twelve weeks because extraction requires negotiated data dumps or chunked monthly CSV batches that extend the extraction phase.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Runple.
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