ERP migration
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
Source
Dolibarr ERP
Destination
Compatibility
8 of 12
objects map 1:1 between Logo Go and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
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 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
Dolibarr ERP
Account (Accounting module)
1:1Logo 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
Dolibarr ERP
ThirdParty (type = Customer)
1:1Logo 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
Dolibarr ERP
ThirdParty (type = Supplier)
1:1Logo 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)
Dolibarr ERP
Product (type = Product or Service)
1:1Logo 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)
Dolibarr ERP
Invoice + AccountingEntry
1:1Logo 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)
Dolibarr ERP
SupplierInvoice + AccountingEntry
1:1Logo 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
Dolibarr ERP
AccountingDocument (various)
1:manyLogo 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
Dolibarr ERP
Asset (if module enabled)
lossyLogo 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
Dolibarr ERP
Tax (various modules)
lossyLogo 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)
Dolibarr ERP
CustomField (Dolibarr)
lossyLogo 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
Dolibarr ERP
Payment
1:1Logo 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
Dolibarr ERP
User
1:1Logo 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.
| Logo Go | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Chart of Accounts | Account (Accounting module)1:1 | Fully supported | |
| Customer | ThirdParty (type = Customer)1:1 | Fully supported | |
| Vendor | ThirdParty (type = Supplier)1:1 | Fully supported | |
| Item (Product/Service) | Product (type = Product or Service)1:1 | Fully supported | |
| Open AR (Accounts Receivable) | Invoice + AccountingEntry1:1 | Fully supported | |
| Open AP (Accounts Payable) | SupplierInvoice + AccountingEntry1:1 | Fully supported | |
| Journal Entry | AccountingDocument (various)1:many | Fully supported | |
| Fixed Asset | Asset (if module enabled)lossy | Fully supported | |
| Tax Configuration | Tax (various modules)lossy | Fully supported | |
| Custom Field (Logo Go) | CustomField (Dolibarr)lossy | Fully supported | |
| Payment Record | Payment1:1 | Fully supported | |
| User/Employee | User1: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.
Logo Go gotchas
Turkish e-Document chain must remain unbroken during migration
Annual LEM dependency for legislative updates
Custom-field schema is per-instance and undocumented
On-premise database access required for clean extraction
App-in-App customisations require source code to migrate
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
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.
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.
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.
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.
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.
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
Logo Go
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. All 8 core objects map 1:1 between Logo Go and Dolibarr ERP.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Logo Go and Dolibarr ERP.
Object compatibility
All 8 core objects map 1:1 between Logo Go 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
Logo Go: Not publicly documented.
Data volume sensitivity
Logo Go 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 Logo Go to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Logo Go
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.