Migrate from Success ERP to Microsoft Dynamics 365 Business Central

Success ERP customer records map to Dynamics 365 Finance and Operations Customer Account. We map customer name, primary contact, GSTIN (to the Tax Identification Number field), billing address, and PAN/TAN where present. Credit limit and payment terms are preserved in custom fields if the export includes them; otherwise they require manual entry in Dynamics 365 after migration because Success ERP sometimes stores these in implementation-partner-specific tables not exposed in standard exports.

Success ERP vendor master records map to Dynamics 365 Vendors entity. Vendor name, PAN/TAN, contact details, and payment terms migrate. We validate GSTIN against India's public GST portal API before inserting and flag any GSTINs that fail validation for customer-side correction. Bank account details for vendor payments migrate to the Vendor bank account table if the export includes them; if not, the customer provides them separately during the migration window.

Success ERP's Indian accounting chart of accounts is exported as a ledger listing with account codes, names, and group assignments. We map each entry to a Dynamics 365 Main Account, preserving the full hierarchy and group mappings so that the COA structure is identical post-migration. We set the Main Account type (Profit and Loss, Balance Sheet, Statistical, etc.) and the account type flag (Financial, Budget, or Statistical) based on the Success ERP account group characteristics. The customer confirms the financial vs statistical type assignment during scoping because this is a business classification that affects reporting.

Success ERP typically operates in INR with no multi-currency setup. We configure Dynamics 365 with INR as the accounting currency and, if the customer requires multi-currency for international transactions, add the relevant currency pairs and exchange rate providers during the configuration phase. Exchange rate providers (configured to pull from the Reserve Bank of India or a commercial provider) require separate setup and are outside the data migration scope.

Success ERP invoice rows are exported as flat transaction records. We split these into Dynamics 365 header-level invoices (with customer, invoice date, payment terms, and tax information at the header) and line items (with item number or ledger account, quantity, unit price, HSN code, and GST tax components). GST amounts and tax breakdown from Success ERP are preserved as tax group assignments and tax detail records in Dynamics 365. Invoices in Completed or Cancelled status are imported with their final state; draft invoices require confirmation on the customer's side about whether to import as open or closed.

Purchase invoices from Success ERP map to Dynamics 365 Vendor Invoice records, with the vendor reference, invoice number, date, and GSTIN verified against the vendor master. If the export includes both purchase orders and vendor invoices, we import Purchase Orders first (as pending receipt) then Vendor Invoices; if only invoice rows are available, we import directly as invoices with a flag for customer reconciliation.

Success ERP Item Master records map to Dynamics 365 Released Products. We preserve item number, description, unit of measure, standard cost, and stock quantities where present in the export. Serial number tracking and batch information migrate only if the export includes those fields, which varies by implementation. Item product type (Item vs Service) is inferred from the item's use in transactions if not explicitly present.

Basic employee records (name, designation, department, and employment status) map to Dynamics 365 Human Resources Worker entity. We map active employees from Success ERP; historical or terminated employees are included only if the customer explicitly requests them and the export contains employment end dates. Worker personal address, contact information, and identification numbers (Aadhaar if present and legally permissible) migrate to the Worker address and identification tables.

Leave balances and payroll history are held in separate export files in Success ERP and must be explicitly requested from the implementation partner. We map leave balance entries to the Dynamics 365 Human Resources leave entitlements table if the customer provides the export. Payroll history (salary components, deductions, and payment records) maps to the Payroll module Worker earning records, but only if a dedicated payroll export file is available; salary details embedded in employee records are treated as approximate and require HR verification post-migration.

If Success ERP exports Purchase Orders as distinct entities (separate from vendor invoices), they map directly to Dynamics 365 Purchase Orders. Purchase Order status migrates as-is (Open, Received, Invoiced, Cancelled). Line items map with vendor, item or ledger account, quantity, and unit cost. We resolve the vendor reference against the imported vendor master before inserting purchase orders.

Success ERP payment term definitions (Net 30, Net 45, etc.) map to Dynamics 365 Payment Terms configuration. We create the equivalent payment term records during the configuration phase and apply them to customer and vendor masters during import. Custom payment terms from Success ERP (e.g., milestone-based terms) are documented for manual entry in Dynamics 365 if they cannot be expressed as a standard day-count definition.

Success ERP's built-in GST setup migrates as a written inventory of tax codes, HSN-code mappings, and GST rate assignments that the customer's Dynamics 365 implementation partner uses to configure the Tax engine in Finance and Operations. We do not configure Dynamics 365's tax engine directly; we provide the complete inventory of GST accounts and rate definitions from Success ERP so the partner can reproduce the tax logic accurately.

Custom fields added by Success ERP implementation partners are not detectable from outside the system. We ask customers to audit their own export files for columns that do not appear in the standard Success ERP schema, and we add any identified custom fields to the mapping as Dynamics 365 custom fields on the equivalent entity. Without the customer's export audit, custom fields are not migrated and require post-migration manual entry.

Documents stored within Success ERP (invoices, purchase orders, employee contracts) are not accessible via documented export mechanisms. We include a manual document checklist in every Success ERP migration plan specifying the record types and approximate count of attachments that require manual download. Customers either extract these directly or request their implementation partner to export the file store. We provide a file-naming convention that maps each document to the equivalent Dynamics 365 record URL for manual re-attachment.