ERP migration
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
Source
Dolibarr ERP
Destination
Compatibility
13 of 15
objects map 1:1 between weclapp erp and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
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 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
Dolibarr ERP
ThirdParty (Client/Supplier)
1:1weclapp 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
Dolibarr ERP
ThirdParty (Client/Supplier)
1:1weclapp 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)
Dolibarr ERP
Product
1:1weclapp 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
Dolibarr ERP
Product stock (Stock movement)
lossyweclapp 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
Dolibarr ERP
Order
1:1weclapp 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
Dolibarr ERP
Order
1:1weclapp 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
Dolibarr ERP
Proposal
1:1weclapp 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)
Dolibarr ERP
Invoice
1:1weclapp 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)
Dolibarr ERP
Invoice (Supplier)
1:1weclapp 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
Dolibarr ERP
Project
1:1weclapp 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
Dolibarr ERP
Document (attached via upload)
1:1Documents 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
Dolibarr ERP
ExtraFields
lossyweclapp 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
Dolibarr ERP
User
1:1weclapp 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)
Dolibarr ERP
Ticket
1:1The 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)
Dolibarr ERP
Contract
1:1The 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.
| weclapp erp | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Customer | ThirdParty (Client/Supplier)1:1 | Fully supported | |
| Company | ThirdParty (Client/Supplier)1:1 | Fully supported | |
| Item (Product/Service) | Product1:1 | Fully supported | |
| Item stock quantities | Product stock (Stock movement)lossy | Fully supported | |
| Sales Order | Order1:1 | Fully supported | |
| Purchase Order | Order1:1 | Fully supported | |
| Quote | Proposal1:1 | Fully supported | |
| Invoice (Sales) | Invoice1:1 | Fully supported | |
| Invoice (Purchase) | Invoice (Supplier)1:1 | Fully supported | |
| Project | Project1:1 | Fully supported | |
| Document attachment | Document (attached via upload)1:1 | Fully supported | |
| Custom Field | ExtraFieldslossy | Fully supported | |
| User | User1:1 | Fully supported | |
| Helpdesk Ticket (Add-on) | Ticket1:1 | Fully supported | |
| Contract (Add-on) | Contract1: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.
weclapp erp gotchas
Excel reformatting corrupts CSV import templates
Add-on modules gate Helpdesk and Contract data
No published API rate limits creates planning uncertainty
Custom fields lack a discovery endpoint
Invoice historical records are immutable after export
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 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.
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.
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.
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.
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.
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
weclapp erp
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. All 8 core objects map 1:1 between weclapp erp and Dolibarr ERP.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across weclapp erp and Dolibarr ERP.
Object compatibility
All 8 core objects map 1:1 between weclapp 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
weclapp erp: Not publicly documented — weclapp states no fixed rate limits exist but does not publish fair-use caps.
Data volume sensitivity
weclapp 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 weclapp erp to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave weclapp 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.