Migrate from Success ERP to Dolibarr ERP

Success ERP Customer records (name, contact phone, email, billing address, GSTIN, payment terms) map to Dolibarr ThirdParty records with the Tiers type set to Customer. GSTIN maps to Dolibarr's ProfId1 field (used for tax identification in India) and ProfId2 maps to PAN if present in the export. We flag any customer records missing GSTIN for customer review before import because Dolibarr's Indian GST module requires a valid GSTIN for e-invoice generation. Credit limits and payment terms from Success ERP require manual confirmation against the export columns since the flat table structure varies by implementation.

Success ERP Vendor records map to Dolibarr ThirdParty with the Supplier type. PAN/TAN, contact details, and bank account information for vendor payments are preserved. Vendor GSTIN maps to ProfId1. Bank account details (account number, IFSC code) must be confirmed as included in the export; these are sometimes stored in a separate ledger table that requires an explicit export request from the Success ERP implementation partner.

Success ERP's Indian accounting ledger export (account codes, names, and group assignments) maps directly to Dolibarr Accounting chart of accounts. Account groups from Success ERP (assets, liabilities, income, expense, group head) are mapped to Dolibarr account subtypes (Comptes de classe 1 through 5 in the French double-entry model, with the Indian GST and TCS accounts assigned to the correct indirect tax liability account codes). The full hierarchy is preserved for reconstruction. If the export includes opening balances, these are set as account movement lines during the first migration phase.

Success ERP sales invoices map to Dolibarr Customer invoices. Invoice header fields (invoice number, date, customer reference, due date) map directly. Line items with HSN codes, GST rates, and tax amounts are preserved as InvoiceLine records. IGST, CGST, and SGST amounts are split into separate tax lines referencing the correct VAT/Sales Tax account in the Dolibarr chart of accounts. We flag any invoices with missing GST details for manual customer review before import because GST-splitting in Dolibarr requires the correct tax account configuration.

Success ERP purchase invoices map to Dolibarr Supplier invoices with the same line-item treatment: HSN codes, GST amounts, and vendor GSTIN on the header. Reverse-charge applicability flags from the source export must be explicitly declared because this information may not be in the standard invoice export and requires vendor confirmation.

Success ERP Item masters with stock quantities, unit of measure, and selling/purchase rates map to Dolibarr Product records. Product type (stockable, service, assembly) is inferred from the export where available. Serial number tracking and batch information are preserved only if those columns are present in the export, which varies significantly by implementation. We add a pre-migration checklist item requiring the customer to confirm whether batch/serial data is included in the item export.

Success ERP Employee records (name, designation, department, salary details) map to Dolibarr User records with the HR module activated. Leave balances, payroll history, PF/ESI deduction records, and TDS details require a separate export file which must be explicitly requested from the Success ERP vendor because these are often in a separate payroll module not included in the standard data export. We flag this as a manual preparation step in the migration kickoff checklist.

GSTR-1 and GSTR-3B summary data from Success ERP maps to Dolibarr accounting ledger entries for GST liability accounts. These are imported as manual journal entries or through the Indian GST accounting module depending on whether the customer has installed the community GST-India module. The migration does not include GSTR e-filing since that is a government portal submission workflow outside Dolibarr's scope.

Project records from Success ERP map to Dolibarr Project if the customer has activated the project management module. Project-to-customer links are preserved as ThirdParty lookups. Project budgets and billing rates migrate as ProjectTask records if the export includes task-level data.

Custom fields added by the Success ERP implementation partner cannot be detected without customer disclosure. We instruct customers to audit their own export reports for any columns they do not recognise before the migration kickoff call. Any custom fields identified are mapped to Dolibarr extrafields if the Dolibarr ThirdParty, Product, or Invoice table has an extrafields extension active, or noted as requiring a PHP developer to add if the base table does not support extrafields.

Documents attached to invoices, purchase orders, employee records, and contracts stored within Success ERP's file storage layer are not accessible via any documented export mechanism. Customers must separately extract these from the platform UI or request their implementation partner to provide the file store. We include a manual document extraction checklist in every Success ERP migration plan so this is not overlooked. Dolibarr's document storage (in /documents/) accepts uploaded files post-migration.

Workflows, approval chains, and automated posting rules built in Success ERP are platform-specific configurations that have no Dolibarr equivalent. We deliver a written inventory of every identified workflow, its trigger condition, and the recommended Dolibarr configuration or community module equivalent. The customer's admin rebuilds these in Dolibarr after migration. Standard accounting post-to-ledger rules are replaced by the Indian GST module's native configuration.