ERP migration
Field-level mapping, validation, and rollback between Streamleader and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
Streamleader
Source
Dolibarr ERP
Destination
Compatibility
10 of 13
objects map 1:1 between Streamleader and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Streamleader to Dolibarr is a structural ERP migration driven by the need for transparent pricing, open-source flexibility, and a visible support community. Streamleader's sales-led flat-rate model at A$300/month hides feature tier definitions behind a contact form, making technical evaluation and API scoping difficult before contract commitment. Dolibarr's community model offers free core modules, paid commercial add-ons, and a modular architecture that activates only what the business needs. We handle the data migration by sequencing exports in dependency order: third-party/Supplier records first, then Customers, then Items, then Chart of Accounts, then open AP/AR records with balance and due-date preservation. Dolibarr's built-in mass import wizard supports CSV ingestion, but custom fields require the CustomFields module configuration before data loads. We do not migrate workflows, automations, or document blobs; we document their locations for manual transfer and deliver a written Dolibarr module activation plan for the customer's admin team.
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 Streamleader 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.
Streamleader
Customer
Dolibarr ERP
ThirdParty (Type = Customer)
1:1Streamleader Customer records map to Dolibarr ThirdParty objects with the Customer type flag set. Customer name, addresses, contact details, and tax IDs migrate to the equivalent Dolibarr fields. We resolve any multi-address structures by creating separate Address records linked via the Address module in Dolibarr. Streamleader's customer-specific custom fields map to Dolibarr ExtraFields (requires CustomFields module activation before import).
Streamleader
Vendor
Dolibarr ERP
ThirdParty (Type = Supplier)
1:1Streamleader Vendor records map to Dolibarr ThirdParty objects with the Supplier type flag. Payment terms, bank details, and supplier-specific metadata migrate to the equivalent Dolibarr fields. We preserve any supplier-specific codes as reference fields. Vendor lookup dependencies for open purchase orders are resolved before invoice import.
Streamleader
Item / Product
Dolibarr ERP
Product
1:1Streamleader Items and Products map to Dolibarr Product records. SKUs, descriptions, pricing, cost, and unit of measure migrate to Product fields. Dolibarr distinguishes between Products (tangible goods) and Services; we determine the type from Streamleader's item classification metadata. Custom pricing tiers in Streamleader map to Dolibarr price lists (requires the Commercial module activation).
Streamleader
Chart of Accounts
Dolibarr ERP
Accounting Account
1:1Streamleader account codes and hierarchies map to Dolibarr Accounting Account objects. Account types (Asset, Liability, Equity, Revenue, Expense) migrate to the corresponding Dolibarr account type. We preserve the full account hierarchy and parent-child relationships. Australian-specific account codes may require reclassification against Dolibarr's French/European default chart; we flag any non-conforming codes for manual review before import.
Streamleader
Open AR Records
Dolibarr ERP
Invoice / Credit Note
1:1Open accounts receivable (customer invoices) migrate to Dolibarr Customer Invoice records with status Open. We preserve original invoice numbers, due dates, total amounts, and line items. Partial payments and credit allocations require balance reconciliation before migration to ensure Dolibarr's aging reports match Streamleader's at cutover. If Streamleader uses a separate payment records object, we consolidate payments against the matching invoice.
Streamleader
Open AP Records
Dolibarr ERP
Supplier Invoice / Credit Note
1:1Open accounts payable (vendor bills) migrate to Dolibarr Supplier Invoice records with status Open. Original vendor invoice references, due dates, amounts, and line items migrate. Credit notes from vendors map to Dolibarr Supplier Credit Notes. Balance reconciliation against Streamleader's vendor ledger confirms accuracy before final commit.
Streamleader
Historical Transactions
Dolibarr ERP
Invoice / Bank Transaction
1:1Transaction history migration depends on Streamleader's retention policy and API pagination capabilities. We attempt date-range chunked exports of closed invoices, payments, and credit notes. Historical bank transactions migrate to Dolibarr Bank Statement entries if Streamleader exposes bank record data. We validate line-item counts against Streamleader's transaction totals and flag any gaps in the export scope.
Streamleader
User
Dolibarr ERP
User
1:1Streamleader User accounts and roles map to Dolibarr User records. Role names and permissions migrate to Dolibarr's permission system (module-level and object-level). We note that Streamleader's Australian-specific role definitions may not map directly to Dolibarr's European-originated permission model; any non-conforming permissions are escalated for manual review. Users without a matching Dolibarr account go to a reconciliation queue for admin provisioning.
Streamleader
Document
Dolibarr ERP
Document (ECM)
1:1Binary document attachments (invoices, receipts, contracts) may not be accessible via Streamleader's undocumented API. We attempt API-based attachment discovery during the technical audit phase. If accessible, documents migrate to Dolibarr's Electronic Content Management (ECM) module with folder structure mapped to the original Streamleader organization. If inaccessible, we document the file locations and recommend manual upload post-migration.
Streamleader
Custom Fields
Dolibarr ERP
ExtraFields
lossyStreamleader custom fields require the Dolibarr CustomFields module (official module from lrq3000/dolibarr_customfields on GitHub) to be installed and configured before any data import. We create matching ExtraFields entries in Dolibarr for each Streamleader custom field, mapping data types (text, number, date, dropdown) to the appropriate Dolibarr field type. This step must complete before record import to avoid schema mismatches.
Streamleader
Currency Settings
Dolibarr ERP
Multi-Currency Configuration
lossyIf Streamleader uses multi-currency (AUD, USD, EUR), we configure Dolibarr's Multi-Currency module before invoice migration. Exchange rate sources are set to match Streamleader's original transaction rates to preserve historical accuracy. Australian Dollar (AUD) is set as the base currency if the business is Australian-localised.
Streamleader
Tax Configuration
Dolibarr ERP
VAT / Tax Configuration
lossyStreamleader's Australian GST configuration (10% GST, BAS reporting) maps to Dolibarr's tax system. We configure the relevant tax codes (TVA/GST equivalent) in Dolibarr's tax configuration before invoice import. Custom tax rates (if any) are preserved as manual tax entries.
Streamleader
Contact
Dolibarr ERP
Contact
1:1Streamleader Contact records attached to Customer or Vendor entities map to Dolibarr Contact records linked via the Contact module. Email, phone, job title, and address details migrate to the matching Dolibarr fields. Multiple contacts per ThirdParty are supported via Dolibarr's contact roles (Billing, Sales, Accounting, etc.).
| Streamleader | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Customer | ThirdParty (Type = Customer)1:1 | Fully supported | |
| Vendor | ThirdParty (Type = Supplier)1:1 | Fully supported | |
| Item / Product | Product1:1 | Fully supported | |
| Chart of Accounts | Accounting Account1:1 | Mapping required | |
| Open AR Records | Invoice / Credit Note1:1 | Fully supported | |
| Open AP Records | Supplier Invoice / Credit Note1:1 | Fully supported | |
| Historical Transactions | Invoice / Bank Transaction1:1 | Mapping required | |
| User | User1:1 | Fully supported | |
| Document | Document (ECM)1:1 | Fully supported | |
| Custom Fields | ExtraFieldslossy | Fully supported | |
| Currency Settings | Multi-Currency Configurationlossy | Fully supported | |
| Tax Configuration | VAT / Tax Configurationlossy | Fully supported | |
| Contact | Contact1: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.
Streamleader gotchas
Sales-led pricing hides feature tier differences
Thin review presence limits due-diligence signals
Document attachment API access undocumented
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 Streamleader account audit
We audit the Streamleader account for object inventory (Customers, Vendors, Items, Chart of Accounts, open AP/AR, Users), custom field definitions, and API access capabilities. If Streamleader's API is undocumented, we perform live endpoint discovery using standard REST patterns and document any access restrictions discovered. We also request Streamleader export confirmation for any objects that require database-level extraction. The discovery output is a written migration scope with record counts, schema map, and a list of objects requiring the CustomFields module.
Dolibarr instance provisioning and module activation
We provision a Dolibarr instance (or validate the customer's existing instance) and activate the required modules: ThirdParty, Product, Invoice, Supplier Invoice, Accounting, Bank, HRM, and ECM. We install the CustomFields module from GitHub and configure ExtraFields entries for each Streamleader custom field. We configure multi-currency settings (if applicable), tax codes, and the base accounting chart before any record import. The instance runs in a staging environment first for validation.
Staging migration and reconciliation
We run a full migration into the staging Dolibarr instance using production-like data volume. The customer reconciles record counts (ThirdParties in, Products in, Invoices in, Accounting entries in), spot-checks 25-50 records against Streamleader source data, and validates account code hierarchies. Any schema corrections, ExtraFields adjustments, or mapping corrections happen in staging before production migration begins. Dolibarr's /install/repair.php is run post-import to clean any database inconsistencies.
User provisioning and permission mapping
We extract distinct Streamleader users and map roles to Dolibarr's permission system. Any Streamleader role without a direct Dolibarr equivalent is escalated for manual permission configuration. The customer's Dolibarr admin provisions active users and sets initial passwords or SSO configuration before production cutover.
Production migration in dependency order
We run production migration in record-dependency order: Accounting Accounts (no dependencies), ThirdParties (Customers and Suppliers), Products and Services, open AP/AR records with balance reconciliation, historical transactions, and Users. Each phase emits a row-count reconciliation report before the next begins. Document attachments are migrated in parallel if the API exposes them, or escalated to manual upload with a documented inventory.
Cutover, validation, and module plan delivery
We freeze Streamleader writes during cutover, run a final delta migration of records modified during the migration window, then enable Dolibarr as the system of record. We deliver a written Dolibarr module activation plan listing recommended modules to enable, recommended module order for activation, and any paid commercial modules (MultiCompany, HRM Advanced, etc.) that match Streamleader feature gaps. We do not rebuild automations or workflows; the plan documents any automation dependencies for the customer's admin to address post-migration.
Platform deep dives
Streamleader
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 Streamleader 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
Streamleader: Not publicly documented.
Data volume sensitivity
Streamleader 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 Streamleader to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your Streamleader 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 Streamleader
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.