Migrate from Growth System to Dolibarr ERP

Growth System Customer records map to Dolibarr Third Party with Type set to Customer. GSTIN stored as a structured field on the Growth System Customer becomes a custom attribute on the Dolibarr Third Party (for example, a custom text field s_gstin). We create the custom field in Dolibarr before migration and import the value from Growth System. Address, phone, email, and contact-person data migrate directly to the Third Party's address and contact tabs. The customer decides during scoping whether to use Dolibarr's built-in contact sub-objects or consolidate to the Third Party record.

Growth System Vendor records map to Dolibarr Third Party with Type set to Supplier. TDS section information stored on the Growth System Vendor migrates to a custom field on the Dolibarr Third Party. GSTIN for vendors also migrates as a custom field. Vendor address, bank details, and contact information follow the same field-level mapping as Customer records.

Growth System's Indian statutory Chart of Accounts does not map directly to Dolibarr's accounting structure. We export the source chart, identify account types (Asset, Liability, Income, Expense, Direct/Indirect), and generate a Dolibarr-compatible CSV import file. Accounts with Indian-specific suffixes (for example, GST Payable, TDS Receivable) are flagged in the handoff document as requiring manual account creation or a localized accounting module from the Dolibarr Dolistore. The customer's local integrator or accountant rebuilds the chart in Dolibarr's Accounting > Chart of Accounts using the CSV as a reference.

Growth System Items map to Dolibarr Products. Growth System's item type (goods vs service) maps to Dolibarr's Product Type (article vs service). Item code becomes Product Reference; item name becomes Product Label. We preserve unit of measure, HSN code as a custom field, and selling/purchase prices from Growth System as Dolibarr MultiPrices if the multi-price module is active.

Growth System inventory valuations and warehouse assignments stored as line-item attributes on stock transactions map to Dolibarr Products with the Stock module enabled. We extract warehouse code and stock quantity from Growth System and import them as Dolibarr Product stock entries (Product-Entrepot records). Stock valuation figures from Growth System are preserved in a migration reference field and reconciled post-import against Dolibarr's stock valuation report.

Growth System stock transactions (receipts, issues, transfers) map to Dolibarr Stock Movement records. Each transaction generates a corresponding StockMouvement record with source warehouse, destination warehouse, product, quantity, and movement date. We batch these chronologically and import via Dolibarr's stock movement import tool to maintain FIFO or weighted-average cost consistency. Large stock transaction histories (over 50,000 records) require chunked import with reconciliation at each batch boundary.

Growth System Sales Invoices map to Dolibarr Facture (Customer Invoice). Invoice number, date, due date, line items (product, quantity, rate, tax, amount), and totals migrate directly. GST amounts from Growth System become tax lines on the Dolibarr invoice. We flag that Dolibarr's invoice PDF output is less customizable than Growth System's; the invoice template rebuild is documented in the handoff package. Invoice status (Draft, Validated, Paid, Cancelled) migrates as-is with the understanding that Dolibarr's workflow requires explicit validation actions post-import.

Growth System Purchase Invoices map to Dolibarr Facture (Supplier Invoice). The same field-level mapping applies as for Sales Invoices, with the vendor linked as a Third Party (Supplier). TDS deduction amounts stored on Growth System purchase invoices become deduction reference notes on the Dolibarr supplier invoice, flagged for manual reconciliation against the reconstructed Chart of Accounts.

Growth System Employee records do not have a direct Dolibarr equivalent if the HR module is not activated. We scope the Dolibarr HR module during discovery: if the customer activates it, Employees map to Dolibarr's Employee object (llx_societe_medicale or llx_employer depending on Dolibarr version). If the HR module is not part of the migration scope, we map Employees to Dolibarr Third Parties (type = Contact) attached to a parent Third Party representing the organization, preserving name, email, phone, and designation as contact attributes.

Growth System Payroll records migrate as Dolibarr Documents linked to the corresponding Employee (or Third Party) if the HR/Salary module is active. If the salary module is not activated in the destination Dolibarr instance, payroll data migrates as a structured CSV handoff with employee reference, period, earnings, deductions, and net pay — for the customer's admin to load into their payroll tool of choice. We do not generate payroll journal entries in Dolibarr's accounting module without explicit scope inclusion.

Growth System Projects map to Dolibarr Project. Project name, description, start date, end date, status, and assigned owner migrate directly. Dolibarr Projects can link to Third Parties (customer), commercial proposals, orders, invoices, and tasks, allowing the customer to rebuild project-centric billing workflows post-migration. Project budget data migrates as custom fields on the Dolibarr Project if the customer requires budget tracking.

Growth System stores GSTIN, TDS section, PF registration, and ESI registration as structured fields on Customer and Vendor records. Dolibarr has no native Indian compliance fields. We create custom fields on the Third Party object (s_gstin, s_tds_section, s_pf_reg_no, s_esi_reg_no) before migration and populate them from Growth System. The handoff document lists these as requiring ongoing maintenance in Dolibarr's Third Party > Extra fields tab. The customer should engage a Dolibarr localizer or Indian compliance consultant for any automated GST filing integration post-migration.