Migrate from SoftLedger to Dolibarr ERP

SoftLedger Locations are the top-level entity container with per-location currency, address, and COA inheritance. Dolibarr has no direct entity object; multi-entity simulation requires the Multi-Company module or manual structure using Third Parties with a category hierarchy and Project tagging. We extract every Location, preserve its currency and address, and map it to a Dolibarr Third Party (as the legal entity) plus a Project or Category node used as the consolidation dimension. Organizations using Dolibarr's Multi-Company module configure it during scoping to mirror the SoftLedger location tree.

SoftLedger COAs are defined per Location with account number, name, type, and tax code. Dolibarr's accountancy module stores a single system-wide COA; per-entity COAs in Dolibarr require either the Multi-Company accountancy module or a category-based tagging strategy on journal lines. We extract each SoftLedger account with its type, number, and tax code, map it to the equivalent Dolibarr account, and flag any accounts that require the Multi-Company module to maintain per-entity segregation.

SoftLedger Customers (name, email, address, payment terms, currency, custom fields) map to Dolibarr Third Parties with type ThirdParty and the Customer checkbox enabled. Payment terms migrate as Dolibarr cond_reglement codes. Currency assignment maps to Dolibarr's multi-currency extra parameters. Custom field values transfer to Dolibarr extra attributes on the Third Party.

SoftLedger Vendors parallel Customer records and include AP-specific fields like 1099 eligibility. We map to Dolibarr Third Parties with the Supplier checkbox enabled. 1099 eligibility flags to Dolibarr's supplier_payment_terms extra attribute. Outstanding AP balances at migration date transfer as open invoice records in Dolibarr's Supplier Invoice module with status Unbilled.

SoftLedger Journal Entries carry Lines with account ID, amount, currency, dimension tags, and source references. We migrate journal lines as Dolibarr Accounting entries (accounting_type = standard). Multi-currency entries require exchange rate extraction: we pull the effective rate at posting date or the manual override rate from SoftLedger metadata and apply it explicitly as Dolibarr's fk_currency rate on each line. Dimension tags from SoftLedger map to Dolibarr categories on the journal line or to project assignment depending on the customer's chosen tagging strategy.

SoftLedger AR Invoices map to Dolibarr Customer Invoice (type invoice customer). Invoice number, date, due date, line items, tax amounts, and status (open, paid, void) migrate directly. Open invoices are migrated with status Unpaid so that outstanding receivables are visible in Dolibarr's AR aging report from day one. Closed invoices migrate as historical records with status Paid and a payment date recorded.

SoftLedger AP Invoices map to Dolibarr Supplier Invoice. The same line-item, tax, and status migration logic applies as AR. Outstanding AP balances migrate as open Supplier Invoices with the appropriate payment term and due date, ensuring that Dolibarr's AP aging reflects the true liability position at cutover.

SoftLedger Bank Transactions link to Journal Entries and carry reconciliation status. We map to Dolibarr Bank Account Statement Lines. Reconciliation status is preserved: unreconciled items are set to open (not reconciled) in Dolibarr so the finance team continues bank reconciliation work without a false-closed bank account. Reconciled items transfer with their reconciliation date and reference intact.

SoftLedger Custom Fields on Customers, Vendors, Invoices, Journal Entries, and other objects are defined during scoping and mapped to Dolibarr extra attributes on the equivalent object. Dolibarr's extra attribute system stores key-value pairs per object ID. We map SoftLedger field types (text, number, select, date) to Dolibarr attribute types and create the attribute definitions in Dolibarr before importing values.

SoftLedger Dimensions tag journal lines with organizational attributes like department or cost center. Dolibarr has no native dimension tagging equivalent; options are Dolibarr Categories (applied to third parties, products, or projects) or Project assignment on individual transactions. We discuss the tagging strategy during scoping: if the customer needs department-level journal-line tagging, we recommend the Multi-Company or custom accounting extension module; if project-level tagging is sufficient, Project assignment covers most use cases.

SoftLedger stores custom report definitions as JSON tied to account IDs. These definitions cannot be imported into Dolibarr's ReportList module because the account ID references are entity-specific. We extract the report JSON configurations and deliver a written document that maps each SoftLedger account ID referenced in a report to its Dolibarr account number, along with instructions for rebuilding the report in Dolibarr's ReportList or via the SQL reporting interface. The customer's admin rebuilds the reports post-migration.

SoftLedger uses a specific Beginning Balance upload mechanism that seeds opening trial balances without posting running transactions. We do not migrate beginning balances as standard journal entries, which would create duplicate balance-sheet impact. Instead, we use SoftLedger's beginning balance endpoint to extract the balance per account per entity, then structure the upload payload to match Dolibarr's opening balance format for the accountancy module. Each entity's opening balance posts as a distinct entry with a designated opening period reference so that the trial balance in Dolibarr reconciles to the SoftLedger snapshot date.