ERP migration

Migrate from Streamleader to Dolibarr ERP

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

Streamleader logo

Streamleader

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

77%

10 of 13

objects map 1:1 between Streamleader and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Streamleader logo

Streamleader

What's pushing teams away

  • Extremely thin review presence (only two verified Capterra reviews) suggests limited market traction and user community
  • No free tier or self-serve pricing makes evaluation risky without a sales conversation first
  • Documentation gaps make technical evaluation difficult before committing to a contract
  • Lack of transparent feature tier definitions means customers may discover limitations only after onboarding
  • Sales-led-only model frustrates teams that prefer self-service evaluation and rapid trial workflows

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

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

maps to

Dolibarr ERP

ThirdParty (Type = Customer)

1:1
Fully supported

Streamleader 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

maps to

Dolibarr ERP

ThirdParty (Type = Supplier)

1:1
Fully supported

Streamleader 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

maps to

Dolibarr ERP

Product

1:1
Fully supported

Streamleader 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

maps to

Dolibarr ERP

Accounting Account

1:1
Mapping required

Streamleader 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

maps to

Dolibarr ERP

Invoice / Credit Note

1:1
Fully supported

Open 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

maps to

Dolibarr ERP

Supplier Invoice / Credit Note

1:1
Fully supported

Open 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

maps to

Dolibarr ERP

Invoice / Bank Transaction

1:1
Mapping required

Transaction 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

maps to

Dolibarr ERP

User

1:1
Fully supported

Streamleader 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

maps to

Dolibarr ERP

Document (ECM)

1:1
Fully supported

Binary 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

maps to

Dolibarr ERP

ExtraFields

lossy
Fully supported

Streamleader 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

maps to

Dolibarr ERP

Multi-Currency Configuration

lossy
Fully supported

If 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

maps to

Dolibarr ERP

VAT / Tax Configuration

lossy
Fully supported

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

maps to

Dolibarr ERP

Contact

1:1
Fully supported

Streamleader 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.).

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.

Streamleader logo

Streamleader gotchas

High

Sales-led pricing hides feature tier differences

Medium

Thin review presence limits due-diligence signals

Medium

Document attachment API access undocumented

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

  • Streamleader API access requires account exploration

    Streamleader publishes no public API documentation, making data extraction scope unknown until the account is accessible. We attempt API discovery during the technical audit phase using standard REST endpoints and observing response shapes. If the API is restricted or undocumented at the customer's contracted tier, we may need to negotiate database-level export access with Streamleader directly or escalate to manual CSV extraction. This risk is escalated before scoping is finalised and may extend the discovery phase by one to two weeks.

  • Dolibarr ExtraFields module required for custom field migration

    Dolibarr's standard installation does not support arbitrary custom fields on objects like ThirdParty, Product, or Invoice. The CustomFields module (lrq3000/dolibarr_customfields on GitHub) must be installed and configured before any record import if Streamleader uses custom fields. We include module installation and ExtraFields configuration in the migration scope but note that this requires Dolibarr admin access and PHP extension compatibility with the Dolibarr version. Without this step, custom field data is lost or truncated.

  • Document blobs may require manual migration

    Streamleader's undocumented document attachment API may not expose binary blobs (invoices, receipts, contracts). We attempt programmatic extraction during audit; if the API returns empty results or access is denied, we document the file locations and recommend manual upload to Dolibarr's ECM module post-migration. This gap is flagged in the migration estimate and does not block core record migration.

  • Dolibarr database migration errors on version upgrade

    Dolibarr's database upgrade scripts have been reported to fail on MySQL/MariaDB configurations with certain collation settings (DB_ERROR_1071: key length exceeds 767 bytes). If the target Dolibarr instance is upgrading from a prior version, we run /install/repair.php after upgrade to clean up orphaned menus, missing fields, and broken ECM entries before migration begins. This is standard practice but adds a validation step to the migration timeline.

  • Australian account codes require reclassification

    Dolibarr ships with French/European accounting default charts. Australian businesses migrating from Streamleader will need to configure a local account structure or adapt the default chart post-migration. We preserve the original Streamleader account codes and hierarchy during export, then flag any non-standard codes for manual reclassification against the desired Australian accounting framework before the Chart of Accounts import is finalised.

Migration approach

Six steps for a successful Streamleader to Dolibarr ERP data migration

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

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

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

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

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

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

Context on both ends of the pair

Streamleader logo

Streamleader

Source

Strengths

  • Flat-rate pricing model (A$300/month) provides cost predictability for small-to-mid-market businesses
  • Australian-localised platform may offer region-specific tax codes, reporting, and compliance features
  • Sales-led engagement allows custom feature negotiations not available on self-serve platforms
  • Positioned as simpler alternative to enterprise ERP suites like Salesforce for SMB use cases

Weaknesses

  • Extremely limited public documentation makes technical evaluation and API assessment difficult pre-purchase
  • Only two verified Capterra reviews indicate low market adoption and sparse user community
  • Sales-only pricing model prevents self-service trials and forces commitment before full feature discovery
  • No published feature tiers means customers may encounter capability gaps after contract signing
  • Limited API visibility restricts automation options and third-party integration flexibility
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. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

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

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • 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

    Streamleader: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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 consultation

Straightforward migrations under 10,000 records with no multi-currency, clean account hierarchies, and API-accessible data land between three and five weeks. Migrations with complex Chart of Accounts structures, multi-currency open invoices, large historical transaction sets, or Streamleader custom fields requiring Dolibarr ExtraFields configuration extend to eight to twelve weeks because of schema discovery time, CustomFields module setup, and AP/AR balance reconciliation.

Adjacent paths

Related migrations to explore

Ready when you are

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