Migrate from Growth System to Acumatica

Growth System uses flat account codes (e.g., 4-001-CASH-INR) that combine the account type, code, and currency into one field. We split these into an Acumatica Account record and a Subaccount dimension, preserving the original code as a reference note on the Account. The Subaccount segment maps to Growth System's cost center dimension when applicable.

Growth System stores customers and vendors as separate entities with address, contact, and GST registration number fields. We map these directly to Acumatica's Customer and Vendor records respectively. The GSTIN field on Growth System customers migrates as a custom field (GSTIN__c) on Acumatica's Customer record since Acumatica uses Taxzone for tax calculation but stores registration numbers as reference fields.

Growth System differentiates between inventory items and non-inventory items by a flag field. We map stock items to Acumatica Stock Items with warehouse tracking enabled and non-stock items to Non-Stock Items. The unit of measure from Growth System translates to Acumatica's UOM class configuration — we match UOM codes first and flag mismatches for your admin to resolve before the full load.

Growth System stores a single warehouse location per item record. Acumatica supports multi-warehouse with bin locations within each warehouse. We map the Growth System warehouse to the primary Warehouse in Acumatica and create a default Bin (the receiving bin) for each. If Growth System tracks sub-locations, we generate additional Bin records and surface them in the migration plan for your review.

Growth System sales invoices map to Acumatica AR Invoice records with the customer, line items, tax amount, and posting date preserved. Payment records from Growth System migrate as Payments applied to the corresponding AR Invoice using the reference number for reconciliation. If Growth System records partial payments as separate receipts, we consolidate them into a single Payment record per invoice in Acumatica.

Growth System purchase invoices map to Acumatica AP Bill records. Receipt transactions that have not yet been invoiced (GRN-based) translate to Acumatica Receipts linked to the vendor. Line-item details including item code, quantity, rate, and tax code are preserved. TDS deductions on Growth System purchase invoices are recorded as a withholding tax on the Acumatica AP Bill.

Growth System stores GSTR filing summaries as transaction metadata. Acumatica generates GST reports from line-level tax transaction data — we cannot migrate the filed-return PDFs as structured records. Instead, we create a custom Tax_Return_Summary__c text area on the GL Transactions for each posting period, storing the GSTR-1 and GSTR-3B summary figures as reference data. Your accountant uses Acumatica's Report Designer to rebuild the filing report from live transaction data.

Growth System TDS deductions on vendor payments map to Acumatica's Withholding Tax feature. We create one Withholding Tax agency in Acumatica per TDS section (e.g., 194, 194C, 194J) and link it to the corresponding AP Bill at the line level. TDS certificate numbers from Growth System are stored in a custom field (TDS_Cert_No__c) on the Acumatica Bill for audit trail purposes.

Growth System employee records (name, employee ID, department, PAN, bank account for salary) migrate as Acumatica Employee records. The PAN number maps to the Employee.TaxFileID field. Bank account details for payroll direct deposit are stored in the Employee.PaymentMethod field — we flag any records missing this data before migration so HR can complete them in Acumatica before the first payroll run.

Growth System's payroll runs generate salary registers with earnings, deductions, and net pay per employee. Acumatica's US/CA payroll edition does not cover Indian payroll compliance (PF, ESI). We migrate the final payroll run summary as a custom Payroll_History__c object with period, employee ID, gross pay, deductions, and net pay — your HR team uses this as the opening balance for payroll in Acumatica or a third-party payroll system post-migration.

Growth System trial balance as of the migration date maps to Acumatica GL Batch entries with the as-of-date preserved. Each account balance becomes a debit or credit GL transaction line in a single batch marked as Opening Balance. We use the original account code as a reference field on each GL Entry so reconciliation back to Growth System is traceable.

Growth System attachments on sales invoices, purchase receipts, and employee records re-upload to Acumatica Files linked to the corresponding document or entity record. File size limits per Acumatica (25MB per file) are enforced during extraction. Inline images in notes are downloaded and rehosted as separate files.

Growth System cost centers map to Acumatica Subaccounts when the relationship is purely for reporting (e.g., departmental P&L). When Growth System uses branches as separate GST-registered entities, we map each branch to an Acumatica Company within a consolidated entity structure — this requires Acumatica inter-company accounting to be enabled and is surfaced in the schema plan before migration.