Migrating from Sage / QuickBooks / SAP B1 to NetSuite

Plan the migration before the implementation starts. Plan and execute a migration from legacy accounting software to NetSuite — data strategy, CoA mapping, CSV import, parallel run, and go-live cutover. 6 hrs · 2 sessions · Intermediate. Overview The largest source of NetSuite implementation failure in the African mid-market is not the configuration — it is the data migration. Organisations underestimate the complexity of moving from Sage, Pastel, QuickBooks, or SAP B1 to NetSuite, leave data cleansing too late, and arrive at the go-live date with a balance sheet that does not balance and a customer list with hundreds of duplicates. This course teaches the migration discipline that prevents those outcomes: how to assess the legacy system for migration complexity, design the data strategy, execute the CSV imports in the right sequence, run a parallel period to validate the results, and complete the cutover with a reconciled opening position. Every step is illustrated with examples from real African NetSuite migrations. Learning outcomes • Assess a legacy accounting system for data migration complexity, data quality risk, and scope decisions • Produce a CoA mapping document from the legacy system to NetSuite with merge, split, and new account decisions • Execute the NetSuite CSV import for customers, vendors, employees, and items in the correct sequence • Post opening balance journal entries reconciled to the legacy system's closing trial balance • Plan and execute a parallel run and a go-live cutover with a complete pre-go-live checklist Prerequisites • Chart of Accounts, Accounting Periods & Financial Settings course or equivalent understanding of NetSuite financial setup • Familiarity with the legacy system being migrated from is strongly recommended Modules 1. Migration assessment, data strategy & the CoA mapping (3 hours) The migration decision: what drives organisations in Africa from Sage, Pastel, QuickBooks, or SAP B1 to NetSuite — scalability, multi-subsidiary requirements, CRM integration, PSA capability, or simply support end-of-life on the legacy product. Common surprises: the data volume that makes a "quick migration" take months, the data quality problems that were hidden by the legacy system's flexibility, and the customisations in the legacy system that NetSuite does not support and must be redesigned. The migration scope decision: the three-tier approach — migrate master data (always), migrate open balances at cutover date (always), migrate historical transactions (rarely, and only for specific reporting needs). The data quality assessment: running the data quality audit on the legacy system — duplicate customers (the Sage deduplication challenge), vendor name inconsistencies, items with no unit cost, employee records with missing mandatory fields. The chart of accounts mapping: producing the mapping document from legacy account codes to NetSuite accounts — the accounts that merge (the legacy system has three bank accounts that become one in NetSuite), the accounts that split (the legacy has one overhead account that NetSuite needs broken into five for reporting), and the accounts that are new (intercompany accounts that did not exist in the single-entity legacy system). Topics: Migration drivers in Africa; Legacy system surprise assessment; Migration scope decision; Three-tier migration approach; Data quality audit; Duplicate customer detection; Vendor name standardisation; Missing mandatory fields; CoA mapping document; Account merge; Account split; New accounts in NetSuite; Migration timeline planning 2. CSV import execution, parallel run & go-live cutover (3 hours) The NetSuite CSV import framework: the import assistant, the import template for each record type, and the required versus optional fields. The correct import sequence: subsidiary (if OneWorld), currencies, CoA (accounts), locations, departments, classes, then customers, vendors, employees, and finally items — and why the sequence matters (customers cannot be imported before their subsidiary exists). Customer import: the fields that matter (name, subsidiary, currency, payment terms, AR account, tax registration number), the common errors (missing required fields, duplicate entity IDs), and the import validation that should run before committing. Vendor import: the same structure, the vendor payment terms, and the WHT code that must be on the vendor record for tax compliance. Item import: the item type field that determines the GL impact, the cost method, the income account, and the asset account. Opening balance journal entries: the approach of posting a single journal entry per GL account as at the cutover date, the sequence (start with the balance sheet, derive the P&L), and the reconciliation to the closing trial balance from the legacy system. Open AR and AP migration: migrating individual open invoices and bills versus posting a single opening balance per customer/vendor — the trade-offs. The parallel run: running both systems for one period (typically one month), comparing the outputs transaction by transaction, and building confidence that NetSuite is producing correct results before switching off the legacy system. The go-live day checklist: the 20 tasks that must be complete before the legacy system is locked, the cutover sequence, and the most common go-live day issues on a legacy-to-NetSuite migration. Topics: CSV import assistant; Import template structure; Required vs optional fields; Import sequence; Subsidiary first; Customer import fields; Common customer import errors; Validation before commit; Vendor import; WHT code on vendor; Item import and GL mapping; Opening balance journal approach; Balance sheet first; Trial balance reconciliation; Open AR/AP migration options; Parallel run design; Transaction-level comparison; Go-live day checklist; Cutover sequence; Common go-live issues Delivery Two sessions, ideally with a week between them for participants to assess their own legacy system between sessions. Best attended by the finance director, the system administrator, and the person who knows the legacy system best (often a long-serving finance officer). Can be run on-site with the client's actual legacy system data for a highly applied experience. Certification Certificate of completion Price USD 700 · per participant per person · indicative · group pricing available HRDC eligibility Up to 75% refundable Mauritius-registered employers may claim this training via the HRDC levy. We provide full documentation to support your claim. Languages English Provider reference SIMPLIT-046-NS_LEGACY_MIGRATION

• Finance directors responsible for the data migration from a legacy system to NetSuite • IT directors or project managers leading the NetSuite implementation • Implementation consultants managing the data migration workstream on a NetSuite project • System administrators responsible for importing master data and opening balances • Accountants who need to understand how historical data will transfer to NetSuite • Any organisation that is currently on Sage 200/300, Pastel, QuickBooks, or SAP B1 and planning a move to NetSuite