ERP migration

Migrate from weclapp erp to Dolibarr ERP

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

weclapp erp logo

weclapp erp

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

87%

13 of 15

objects map 1:1 between weclapp erp and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from weclapp ERP to Dolibarr is a structural consolidation, not a record copy. weclapp organizes data across three bundles (Starter at €39, Services at €84, Trade at €159 per user per month) with separate add-ons for Helpdesk and Contract Management; Dolibarr's modular architecture activates only the features each business needs at €14-€30 per user per month through DoliCloud or self-hosted. We export master data through weclapp's CSV wizard (format-free, never through Excel to avoid column reformatting), validate record counts against the source, and load through Dolibarr's native import paths or database INSERT for high-volume objects. Paid invoices migrate as locked records to preserve accounting integrity. We do not migrate workflows, automations, or DATEV integration configurations; these require manual reconfiguration at the destination and are documented in our handoff package.

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

weclapp erp logo

weclapp erp

What's pushing teams away

  • Navigation between views opens new browser tabs rather than inline transitions, creating workflow friction that accumulates over time for power users.
  • Value for money scores lag behind competitors — several review sources note pricing feels steep relative to what comparable platforms charge for equivalent feature sets.
  • Support quality is inconsistent — Capterra reviews show a 3.9/5 for customer service, with some users reporting slow resolution times outside premium support tiers.
  • Limited reporting depth compared to purpose-built BI tools — teams needing advanced analytics often export to Peliqan or Tableau rather than relying on weclapp's native dashboards.
  • Difficulty scaling beyond mid-market complexity — companies with growing international operations or multi-entity structures find themselves outgrowing weclapp's structure.

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

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

weclapp erp

Customer

maps to

Dolibarr ERP

ThirdParty (Client/Supplier)

1:1
Fully supported

weclapp Customers map to Dolibarr ThirdParty records with type ThirdParty.properties性子 = Client. The customer's name, address, email, phone, and tax ID (USt-IdNr for German VAT) migrate directly. We use the ThirdParty.email as the dedupe key during import and resolve any duplicates against existing Dolibarr records before insert. Note that weclapp distinguishes Customers (individuals) from Companies (B2B accounts); Dolibarr uses a single ThirdParty object with a Type field to distinguish them.

weclapp erp

Company

maps to

Dolibarr ERP

ThirdParty (Client/Supplier)

1:1
Fully supported

weclapp Company records (B2B accounts) map to Dolibarr ThirdParty with type = Company. We preserve the associated contacts by linking them to the same ThirdParty record via Dolibarr's contact submodule. The company's website, address, and any contact links migrate as structured data. If weclapp has a separate main-contact flag, we set that contact as the default for the ThirdParty.

weclapp erp

Item (Product/Service)

maps to

Dolibarr ERP

Product

1:1
Fully supported

weclapp Items (products and services) map to Dolibarr Product records. Weclapp's SKU, description, unit price, and stock quantity map to Dolibarr's ref, label, price, and pmp (weighted average cost). Services in weclapp with no stock quantity map to Dolibarr Products with type = Service. If weclapp uses pricing tiers, we migrate the base price and flag the tiered structure for manual re-entry or Dolistore pricing module activation at the destination.

weclapp erp

Item stock quantities

maps to

Dolibarr ERP

Product stock (Stock movement)

lossy
Fully supported

weclapp Trade tier stores multi-warehouse stock with per-warehouse quantities. Dolibarr's stock module uses a single warehouse model with stock movements recorded per product. We flatten the multi-warehouse quantities into Dolibarr's stock_reel table entries under a single default warehouse (or multiple warehouses if the destination has them pre-configured). Stock value at cost migrates to Dolibarr's pmp field. Multi-warehouse mapping is a configuration step confirmed during scoping.

weclapp erp

Sales Order

maps to

Dolibarr ERP

Order

1:1
Fully supported

weclapp Sales Orders map to Dolibarr Commande records with type = CustomerOrder. We preserve line items (product references, quantities, unit prices), order status, and the linked Customer reference. Historical closed orders migrate as read-only records; open orders remain open for continued processing in Dolibarr. The order date and delivery date map to Dolibarr's date_creation and delivery_date fields.

weclapp erp

Purchase Order

maps to

Dolibarr ERP

Order

1:1
Fully supported

weclapp Purchase Orders map to Dolibarr Commande records with type = SupplierOrder. The linked vendor record (from weclapp Companies with supplier role) must be present as a Dolibarr ThirdParty before the Purchase Order inserts. Line items, agreed prices, and quantities migrate directly. Closed Purchase Orders migrate as historical records.

weclapp erp

Quote

maps to

Dolibarr ERP

Proposal

1:1
Fully supported

weclapp Quotes (Sales Quotations) map to Dolibarr Propal records. Validity dates, pricing, and status migrate. If the quote has been accepted and converted to a Sales Order, we create both the Proposal and the resulting Order in Dolibarr to preserve the conversion history. Quotes with status = Draft migrate as Draft; Accepted quotes migrate as Open with validity flags preserved.

weclapp erp

Invoice (Sales)

maps to

Dolibarr ERP

Invoice

1:1
Fully supported

weclapp Sales Invoices map to Dolibarr Facture records. Paid invoices migrate as locked records (statut = Closed, paye = 1) to preserve accounting integrity. The payment date and payment method from weclapp map to Dolibarr's date_payment and fk_paiement fields. Unpaid invoices migrate as Open with payment terms preserved. Tax codes from weclapp must be mapped to Dolibarr's VAT rate configuration, which is a manual setup step documented in our handoff package.

weclapp erp

Invoice (Purchase)

maps to

Dolibarr ERP

Invoice (Supplier)

1:1
Fully supported

weclapp Purchase Invoices map to Dolibarr Facture (Fournisseur) records. The linked vendor ThirdParty must be inserted before the invoice. Paid purchase invoices migrate as closed records. Unpaid purchase invoices carry the vendor reference and payment terms. Currency handling in weclapp (multi-currency invoices) maps to Dolibarr's multicurrency fields if the multi-currency module is enabled.

weclapp erp

Project

maps to

Dolibarr ERP

Project

1:1
Fully supported

weclapp Projects map to Dolibarr Project records. Tasks nested under the project migrate as Dolibarr Tasks linked to the same Project. Time entries from weclapp Services tier map to Dolibarr ProjectTaskTime records if the time tracking module is enabled. Project status workflow (Active, On Hold, Closed) migrates directly. We flag the project header structure so the customer can verify task hierarchy in Dolibarr before go-live.

weclapp erp

Document attachment

maps to

Dolibarr ERP

Document (attached via upload)

1:1
Fully supported

Documents attached to Customers, Orders, Invoices, or Projects in weclapp export as binary files. We map them to Dolibarr's document management submodule by re-uploading each file to the correct record in Dolibarr and preserving the original filename. Attachment metadata (upload date, uploaded by user) migrates as Dolibarr extrafields if the ECM (Electronic Content Management) module is enabled.

weclapp erp

Custom Field

maps to

Dolibarr ERP

ExtraFields

lossy
Fully supported

weclapp allows custom fields on most standard objects but has no unified discovery endpoint. We enumerate active custom fields per object type during the discovery phase by querying object metadata individually. Each custom field is exposed as a Dolibarr Extrafields definition on the target object (ThirdParty, Product, Commande, Facture, etc.) and populated during record import. Fields with no Dolibarr equivalent are flagged for manual re-entry or Dolistore module activation.

weclapp erp

User

maps to

Dolibarr ERP

User

1:1
Fully supported

weclapp Users map to Dolibarr Users by email match. Active users in weclapp provision as active Dolibarr users; deactivated users migrate as inactive or are excluded per the customer's scoping choice. User roles and permissions in weclapp have no direct Dolibarr equivalent and are documented separately for the admin to reconfigure.

weclapp erp

Helpdesk Ticket (Add-on)

maps to

Dolibarr ERP

Ticket

1:1
Fully supported

The Helpdesk add-on must be confirmed active during scoping. If present, weclapp tickets map to Dolibarr Ticket records with linked ThirdParty (customer) and assigned User (agent). Ticket status, priority, and conversation threads migrate as Ticket objects. This object is only available on weclapp plans with the Helpdesk module purchased; we warn the customer during scoping if the module is absent and adjust scope accordingly.

weclapp erp

Contract (Add-on)

maps to

Dolibarr ERP

Contract

1:1
Fully supported

The Contract Management add-on must be confirmed active during scoping. If present, weclapp contracts map to Dolibarr Contract records linked to the associated ThirdParty. Contract status, start date, end date, and attached documents migrate. The contract renewal workflow state may need manual reconfiguration in Dolibarr depending on the complexity of the source workflow.

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.

weclapp erp logo

weclapp erp gotchas

High

Excel reformatting corrupts CSV import templates

Medium

Add-on modules gate Helpdesk and Contract data

Medium

No published API rate limits creates planning uncertainty

Medium

Custom fields lack a discovery endpoint

Low

Invoice historical records are immutable after export

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

  • Excel silently corrupts weclapp CSV export files

    weclapp's import wizard uses exact column formats for CSV files, but Microsoft Excel silently reformats columns when opening CSV exports, converting dates to mm/dd/yyyy, phone numbers to numeric-only strings, and long fields to scientific notation. This produces CSV files that pass basic validation but fail import or corrupt records at Dolibarr. We always open weclapp CSV exports format-free using the platform's published method or a text editor and validate column integrity before ingestion. This step prevents records importing with malformed dates or phone numbers that pass Dolibarr's import wizard but fail in production.

  • Multi-warehouse stock flattens to single warehouse in Dolibarr

    weclapp Trade tier supports multiple warehouses with per-warehouse stock quantities and transfer workflows. Dolibarr's standard stock module uses a single warehouse model with stock_reel entries representing quantity on hand. When migrating from a multi-warehouse weclapp Trade account, we consolidate warehouse quantities into a single Dolibarr warehouse or map them to multiple pre-configured Dolibarr warehouses if the destination has them defined. This transformation is a configuration decision confirmed during scoping and adds discovery time for accounts with more than three warehouses.

  • Helpdesk and Contract Management add-ons gate data availability

    Helpdesk and Contract Management are paid add-ons on weclapp not available on all plan tiers. During migration scoping we confirm which add-ons are active in the source account. If the Helpdesk module is absent, we warn the customer that ticket records are not present in the export and remove them from the migration scope. Similarly, if Contract Management is absent, contracts do not exist in the export. We do not create placeholder structures for unused add-on slots; the scope reflects what actually exists in the source data.

  • Paid invoices must not be re-activated at destination

    weclapp marks paid and closed invoices as immutable for accounting integrity. When we export historical invoices to Dolibarr, they arrive as Facture records with payment_date and payment_method populated and should not be reopened. We flag any records with payment_date in the past as locked during migration planning and document them as read-only in the handoff package. Re-opening a reconciled invoice in Dolibarr would create a double-posting risk in financial reports.

  • DATEV integration does not migrate and requires replacement

    weclapp's native DATEV export is a DACH-region feature for German accountant handoff that has no equivalent in Dolibarr's core module set. Community-developed DATEV export modules exist on Dolistore but require manual installation and configuration at the destination. We do not migrate the DATEV configuration as code. We document the DATEV export settings in the handoff package so the customer can evaluate and install a Dolistore module or configure manual export procedures with their accountant.

Migration approach

Six steps for a successful weclapp erp to Dolibarr ERP data migration

  1. Discovery and add-on availability check

    We audit the source weclapp account across plan tier (Starter, Services, Trade), active add-ons (Helpdesk, Contract Management), record counts per object, custom field usage per object type, and CSV export template availability. We open CSV exports format-free to validate column integrity before ingestion. The discovery output is a written migration scope confirming which objects have data to migrate, which add-ons are active, and whether multi-warehouse stock is in scope. If the Helpdesk or Contract Management add-on is absent, we remove that object from scope and confirm with the customer before proceeding.

  2. Dolibarr module activation and schema configuration

    We work with the customer's Dolibarr administrator to activate the appropriate modules before migration: ThirdParty (CRM), Product, Stock, Commande, Facture, Project, Ticket (if helpdesk add-on was active in source), Contract (if contract add-on was active), and ECM (for document attachments). We configure VAT rates to match the tax codes present in weclapp invoices, create the default warehouse for stock migration, and pre-create any Extrafields definitions matching the enumerated custom fields from weclapp. Module activation happens in a test environment first for validation.

  3. Format-free CSV preprocessing and record reconciliation

    We open every weclapp CSV export format-free and validate column headers against the expected import template. We transform weclapp date formats to ISO 8601 (YYYY-MM-DD) before import, strip any Excel reformatting artifacts from numeric and phone columns, and resolve foreign-key references (customer IDs on orders, item IDs on line items) against the extracted lookup tables. The preprocessing step emits a clean CSV per object with a record-count reconciliation report against the source.

  4. Dolibarr import in dependency order

    We load records into Dolibarr in dependency order: ThirdParty (Companies and Customers, with type flags set), Product (Items with stock quantities), Project (headers only), then transactional records (Sales Orders, Purchase Orders, Quotes, Invoices, Projects with tasks), then attachments, then add-on objects (Tickets, Contracts) if applicable. Each phase emits a row-count reconciliation report. For high-volume objects (over 5,000 records), we use Dolibarr's batch import wizard with CSV files; for very large volumes we use direct database INSERT with referential integrity validated after each batch.

  5. Sandbox migration and customer reconciliation

    We run a full migration into the customer's Dolibarr test environment before production. The customer's team reconciles record counts per object, spot-checks 25-50 random records against the weclapp source, and verifies that linked records (orders to customers, invoices to contacts) resolved correctly. Any mapping corrections are documented and applied to the production migration plan. This step ensures that the production migration runs on validated assumptions rather than first-pass logic.

  6. Production migration, cutover, and handoff

    We freeze writes in weclapp during the production cutover window, run a delta export of any records modified since the initial extract, and load the final delta into Dolibarr. We verify record counts match across all objects, confirm invoice totals in Dolibarr against source reports, and deliver the handoff package including the workflow and automation inventory (for manual rebuild), the DATEV configuration documentation, and the user role mapping sheet. We do not rebuild weclapp workflows, automations, or e-commerce sync configurations in Dolibarr; these are documented for the customer's admin to reconfigure.

Platform deep dives

Context on both ends of the pair

weclapp erp logo

weclapp erp

Source

Strengths

  • DATEV accounting integration natively built in, eliminating manual accountant handoff for German businesses.
  • Modular add-ons (Helpdesk, Contract Management, Mobile Warehouse) stack onto a single base subscription.
  • No published API rate limits, giving FlitStack AI flexible throughput during large-volume migrations.
  • CSV import/export wizard covers all master-data objects with structured templates under Global Settings.
  • Form designer allows per-company customization of document layouts and workflow states.

Weaknesses

  • CSV import templates are fragile — Excel reformats columns on open, requiring format-free preprocessing.
  • Custom fields exist on most objects but there is no unified custom-field registry to enumerate before migration scoping.
  • Helpdesk and Contract Management add-ons are not available on all plans, creating feature gaps when migrating from lower tiers.
  • Multi-entity or multi-company structures are not natively supported, requiring manual data partitioning at the destination.
  • Support quality on free and lower-tier packages is inconsistent, complicating migration assistance requests.
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 weclapp erp and Dolibarr ERP.

B

Overall complexity

Standard migration

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

  • Object compatibility

    A

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

    weclapp erp: Not publicly documented — weclapp states no fixed rate limits exist but does not publish fair-use caps.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your weclapp 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 10,000 customer records and 5,000 items with no add-on data and clean CSV exports. Migrations with the Helpdesk or Contract Management add-ons active, Trade-tier multi-warehouse stock, or large order and invoice histories (over 20,000 transactional records) move to eight to twelve weeks because of multi-warehouse consolidation, add-on record mapping, and extended reconciliation. The timeline also extends if custom field enumeration requires querying each object type individually during discovery.

Adjacent paths

Related migrations to explore

Ready when you are

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