ERP migration

Migrate from Logo Go to Dolibarr ERP

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

Logo Go logo

Logo Go

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

67%

8 of 12

objects map 1:1 between Logo Go and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Logo Go to Dolibarr addresses two core limitations: Logo Go's minimal documented API surface and its regional-market constraints. Dolibarr's open-source core provides a documented REST API, a modular architecture with commercial add-ons, and an active community that reduces vendor lock-in. We extract Logo Go data via direct database access and CSV dumps where the API is unavailable, normalize the Chart of Accounts and tax codes into Dolibarr's accounting module structure, and map customers and vendors to Dolibarr's ThirdParty object. Open AP/AR balances transfer as accounting entries with the original invoice references preserved. We do not migrate Logo Go's local workflows or localized Turkish reporting templates; we deliver a written inventory of these for the customer's admin to rebuild in Dolibarr's module system.

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

Logo Go logo

Logo Go

What's pushing teams away

  • Annual LEM (maintenance & update) fees are mandatory on top of licence cost — total cost of ownership creeps up year over year.
  • On-premise architecture (Windows desktop / web client) is increasingly out of step with cloud-first competitors; multi-site and remote-access deployments require extra infrastructure work.
  • Public API and developer documentation are sparse — App-in-App technology exists for Logo partners but is not openly published, limiting third-party integration vendors outside Turkey.
  • Heavy localisation to Turkish accounting and tax practice creates friction when companies expand internationally or run multi-country consolidations.
  • Modular pricing differences between 1-user and 10-user configurations are significant — growth above 10 users triggers package upgrades that surprise buyers at renewal.

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

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

Logo Go

Chart of Accounts

maps to

Dolibarr ERP

Account (Accounting module)

1:1
Fully supported

Logo Go Chart of Accounts records map to Dolibarr's accounting Account entries under Bank, Cash, Creditors, Debtors, and Miscellaneous account types. Account codes from Logo Go transfer as Dolibarr pcg_type and pcg_subtype classifications. We preserve the account nature (asset, liability, expense, revenue) and assign the corresponding Dolibarr account type. Active and passive account flags migrate as Account.active status.

Logo Go

Customer

maps to

Dolibarr ERP

ThirdParty (type = Customer)

1:1
Fully supported

Logo Go Customer records map to Dolibarr ThirdParty with customer status enabled. Address, phone, email, and tax identification number transfer to Dolibarr's address fields and thirdparty-specific properties. The Logo Go customer code becomes the ref_internal field in Dolibarr. Country and state codes normalize to Dolibarr's country_id and state_id lookup values. Customers without email receive a placeholder note flagging manual contact verification.

Logo Go

Vendor

maps to

Dolibarr ERP

ThirdParty (type = Supplier)

1:1
Fully supported

Logo Go Vendor records map to Dolibarr ThirdParty with supplier status enabled. The vendor code maps to ref_supplier, and the Logo Go vendor classification (local, import) transfers as a custom field or tag in Dolibarr. Tax identification and bank account details migrate to Dolibarr's rib (bank account) records attached to the ThirdParty. Vendor ledger balances migrate as Creditor accounting entries.

Logo Go

Item (Product/Service)

maps to

Dolibarr ERP

Product (type = Product or Service)

1:1
Fully supported

Logo Go Items map to Dolibarr Product records with type set to Product (for inventory-tracked goods) or Service (for non-stocked items). The Logo Go item code becomes ref, and the item description becomes label. Units of measure from Logo Go map to Dolibarr's unit_of_measure field. Cost price and selling price migrate as pmp (average cost) and price_ttc (all-in price) respectively.

Logo Go

Open AR (Accounts Receivable)

maps to

Dolibarr ERP

Invoice + AccountingEntry

1:1
Fully supported

Logo Go open AR records transfer as Dolibarr Customer Invoice records with status = unpaid. The original invoice number from Logo Go becomes ref_client on the Dolibarr invoice. Outstanding balance and due date migrate to remaintopay and datedue fields. Each invoice generates a corresponding accounting line entry linking to the Debtors account. We flag any AR record with a Logo Go payment term that does not map directly to a Dolibarr payment term condition.

Logo Go

Open AP (Accounts Payable)

maps to

Dolibarr ERP

SupplierInvoice + AccountingEntry

1:1
Fully supported

Logo Go open AP records transfer as Dolibarr Supplier Invoice records with status = unpaid. The vendor invoice number becomes ref_supplier. Outstanding balance migrates to remaintopay on the supplier invoice. Each supplier invoice generates an accounting line entry linked to the Creditors account. We preserve the original vendor name and invoice date for audit trail purposes.

Logo Go

Journal Entry

maps to

Dolibarr ERP

AccountingDocument (various)

1:many
Fully supported

Logo Go journal entries represent the most complex migration object. We extract each journal line (account, debit, credit, description, date) and reconstruct them as Dolibarr accounting documents. Where Logo Go uses custom journal types, we map to the nearest Dolibarr journal type (sale, purchase, bank, cash, opening). Lines without a matching Dolibarr account code go to a reconciliation queue for the customer's accountant to resolve post-migration.

Logo Go

Fixed Asset

maps to

Dolibarr ERP

Asset (if module enabled)

lossy
Fully supported

Logo Go fixed asset records (asset name, acquisition date, cost, accumulated depreciation, depreciation method) map to Dolibarr's Asset module if it is activated. If the Asset module is not enabled in the destination Dolibarr instance, we migrate asset records as Product entries with a custom asset flag and deliver a written plan for Asset module configuration. Acquisition cost and accumulated depreciation transfer as separate fields to allow the customer's accountant to verify the depreciation schedule post-migration.

Logo Go

Tax Configuration

maps to

Dolibarr ERP

Tax (various modules)

lossy
Fully supported

Logo Go's Turkish-localized tax codes (KDV rates, ÖTV where applicable) map to Dolibarr's tax setup. We extract each distinct tax rate from Logo Go's configuration, map it to a corresponding Dolibarr tax type, and assign it to the relevant product categories. Any Logo Go tax exemption codes become Dolibarr tax exemption conditions. We flag any tax rule that references Turkish-specific fiscal categories not available in Dolibarr's base tax module.

Logo Go

Custom Field (Logo Go)

maps to

Dolibarr ERP

CustomField (Dolibarr)

lossy
Fully supported

Logo Go custom fields map to Dolibarr's CustomFields module. We extract the field name, data type, and value from Logo Go's database (since public API access to custom fields is limited) and create equivalent Dolibarr custom field definitions before record migration. Field types map by closest Dolibarr equivalent: text fields become varchar, numeric fields become price or integer, date fields become date. The customer's admin reviews the custom field mapping during sandbox validation.

Logo Go

Payment Record

maps to

Dolibarr ERP

Payment

1:1
Fully supported

Logo Go payment records (payment date, amount, payment method, reference) map to Dolibarr Payment records linked to the corresponding invoice. We resolve the parent invoice reference at migration time using the invoice mapping table created during the scoping phase. Payment method codes from Logo Go map to Dolibarr payment terms (tipa for bank transfer, cash for cash payments, cheque for checks). Partial payments attach to the corresponding invoice's partial payment record.

Logo Go

User/Employee

maps to

Dolibarr ERP

User

1:1
Fully supported

Logo Go user and employee records map to Dolibarr User accounts. We extract the username, email, and role from Logo Go and create corresponding Dolibarr User accounts with the appropriate permission set (read, write, admin). If Logo Go uses department or cost-center assignments, these migrate as Dolibarr Project or Tags assignments for reporting purposes. User status (active, inactive) transfers directly.

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.

Logo Go logo

Logo Go gotchas

High

Turkish e-Document chain must remain unbroken during migration

High

Annual LEM dependency for legislative updates

Medium

Custom-field schema is per-instance and undocumented

Medium

On-premise database access required for clean extraction

Low

App-in-App customisations require source code to migrate

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

  • Logo Go's limited API requires direct database extraction

    Logo Go's public API documentation is extremely limited, which means most migrations require direct database access or CSV exports from the application layer. We coordinate with the customer's Logo Go administrator to obtain a database read-only account or export credentials. If the Logo Go database is hosted on a proprietary or unsupported SQL variant, we adapt the extraction query. Data extracted this way must be validated against the application layer because the database schema may have undocumented column dependencies. This extraction step adds one to two weeks to the timeline compared to migrations from platforms with documented REST APIs.

  • Turkish tax codes require manual normalization for Dolibarr

    Logo Go's tax configuration is built around Turkish regulatory requirements (KDV rates at 1%, 8%, 18%, and any exemption categories). Dolibarr's base tax module supports multi-country VAT but does not ship with pre-configured Turkish tax rates. We extract the active tax rates from Logo Go, create corresponding Dolibarr tax types, and assign them to product categories during the configuration phase. The customer's accountant reviews and validates the tax mapping before production import. Any Turkish-specific levies (ÖTV, SCT) that do not map to standard VAT require a custom solution or manual journal entry after migration.

  • Dolibarr's logo upload has a known storage-path issue

    Dolibarr versions through at least v19 have a documented bug where company logos and third-party logos do not load correctly after server migration or directory restructure (GitHub issues #34922 and #10296). The symptom is a broken logo image on invoices and third-party cards. The cause is typically a mismatch between the document directory path in conf.php and the actual storage location. We configure the Dolibarr document root explicitly during installation and test logo rendering in the sandbox before production cutover. If logos were already migrated from Logo Go, we verify the storage path after each migration phase.

  • Third-party Dolibarr modules may break on version upgrades

    Dolibarr's modular architecture means that commercial or community add-ons can become incompatible after a Dolibarr version upgrade. The Dolibarr forum documents cases where external modules (marketplace add-ons, custom modules) fail to load or cause Error 500 after upgrading the core Dolibarr installation. We recommend upgrading Dolibarr on a staging environment first, running the Dolibarr database migration scripts completely, and verifying all modules before applying the upgrade to production. We do not upgrade Dolibarr as part of the migration scope unless explicitly contracted; we flag the current version and recommend a post-migration upgrade plan if the source Dolibarr instance is running an older release.

  • Logo Go journal entries may have non-standard account references

    Logo Go's chart of accounts often contains account codes that were created for specific Turkish regulatory reporting requirements and may not have a direct Dolibarr equivalent. Journal entries referencing these codes must be reconciled by the customer's accountant before they can be posted in Dolibarr. We extract all journal entry lines with unmatched account codes into a reconciliation report during the sandbox migration. The customer resolves each line in Logo Go or approves an account code mapping before production migration. We do not post unmatched journal lines in Dolibarr without explicit customer approval, as posting invalid account codes can cause accounting errors that are difficult to reverse.

Migration approach

Six steps for a successful Logo Go to Dolibarr ERP data migration

  1. Logo Go data extraction scoping

    We work with the customer's Logo Go administrator to identify the database type (MSSQL, MySQL, or proprietary), obtain read-only database credentials or export access, and document the schema. We run exploratory queries against the Logo Go database to identify custom field storage locations, tax configuration tables, journal entry structure, and fixed asset records. We also request CSV exports of Chart of Accounts, Customers, Vendors, Items, and Open AP/AR from the Logo Go application layer as a cross-validation against the database query results. The scoping output is a written data extraction plan and a preliminary field map for Dolibarr.

  2. Dolibarr instance provisioning and module activation

    We provision the destination Dolibarr instance (self-hosted on the customer's server or via DoliCloud) and activate the modules required for migration: ThirdParty (for customers and vendors), Product (for items), Facture (for invoices), Accounting (for chart of accounts and journal entries), Bank (for payment records), and Asset (if fixed assets are in scope). We configure the company information, fiscal year, currency (TRY or multi-currency if applicable), and tax setup during this phase. Dolibarr's database upgrade scripts run automatically on first activation; we verify completion and check the Dolibarr version against the requirements.

  3. Custom field definition in Dolibarr

    We extract Logo Go custom field definitions from the database (field name, data type, associated object) and create equivalent Dolibarr CustomFields module entries before any record data is loaded. Each custom field is assigned to the correct Dolibarr object (ThirdParty, Product, Facture) and typed to match the data (varchar, int, date, select). We validate that the custom field values in Logo Go will fit within the Dolibarr field length constraints. The customer reviews and approves the custom field mapping during the sandbox review.

  4. Sandbox migration and reconciliation

    We run a full migration into a staging Dolibarr instance using the extracted Logo Go data. We migrate Accounts, ThirdParties, Products, Invoices, and Payments in dependency order, then run reconciliation queries to compare record counts, outstanding balances, and journal totals between Logo Go and Dolibarr. The customer's accountant spot-checks 25-50 records per object type and validates that the Dolibarr invoice PDFs match the original Logo Go format. Any mapping corrections (account codes, tax rates, payment terms) are applied to the transform scripts before production migration begins.

  5. Production migration in dependency order

    We run the production migration in the sequence: Chart of Accounts, ThirdParties (Customers then Vendors), Products, Customer Invoices, Supplier Invoices, Payments, Journal Entries, and Custom Fields. Each phase emits a row-count and balance-reconciliation report before the next phase begins. We freeze Logo Go write access during the production migration window. Any records modified in Logo Go during migration are captured in a delta pass after the initial bulk load. Journal entries with unresolved account codes are held in a queue for customer approval before posting.

  6. Cutover, validation, and configuration handoff

    We enable Dolibarr as the system of record after the final reconciliation pass. We verify that the Dolibarr accounting trial balance matches the Logo Go trial balance within tolerance (typically under 0.1% variance for balance sheet accounts). We deliver a written inventory of any Logo Go workflows, Turkish-specific reporting templates, or localized fiscal documents that cannot migrate automatically, with recommendations for Dolibarr module configuration to support them. We support a one-week hypercare window for reconciliation issues raised by the customer's team. We do not rebuild Logo Go workflows or Turkish tax reporting templates as part of the migration scope; these are documented for the customer's admin or a Dolibarr partner to implement post-migration.

Platform deep dives

Context on both ends of the pair

Logo Go logo

Logo Go

Source

Strengths

  • Native Turkish e-Document compliance (e-Fatura, e-Defter, e-Arsiv, e-Irsaliye) and GIB integration out of the box
  • Single-platform coverage of finance, accounting, sales, purchasing, inventory and reporting for SMEs
  • Modular 'pay for what you use' licensing keeps entry cost low compared to SAP Business One
  • Integrates with the Logo ecosystem (CRM, Payroll Plus, Mind Insight, Flow) for downstream growth
  • Industry-independent design serves distribution, construction, education, textiles, media and healthcare

Weaknesses

  • Annual LEM maintenance fee is mandatory on top of licence cost; lapsing it breaks compliance updates
  • On-premise Windows architecture lags cloud-first competitors for remote-work and multi-site deployments
  • Public API documentation is sparse; partner integrations rely on App-in-App customisation rather than open REST
  • Heavy Turkish localisation creates friction for multi-country or international expansion
  • Pricing escalates significantly between 1-user and 10-user package tiers, surprising growing customers at renewal
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 Logo Go and Dolibarr ERP.

B

Overall complexity

Standard migration

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

  • Object compatibility

    A

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

    Logo Go: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your Logo Go to Dolibarr ERP migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Logo Go to Dolibarr migrations land between three and five weeks for accounts with up to 10,000 general ledger rows, 2,000 customers, 1,500 vendors, and 3,000 items. Migrations requiring complex journal entry reconstruction, multi-year AP/AR carry-forward, fixed asset schedule migration, or extensive Turkish tax code normalization move to seven to twelve weeks. The primary variable is whether direct database access to Logo Go is available and whether the database schema is documented; limited API access is the single largest timeline risk for this pair.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Logo Go.
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