Sage Intacct Premier Partner — South Africa
    All services
    05

    Data Migration

    The hardest part of any ERP move is the data. We've done this many times.

    Bo Gartner has migrated to Sage Intacct from Pastel Partner, Pastel Evolution, Sage 50, Sage 200, QuickBooks Online, Xero, and a handful of bespoke ERPs. Every migration ends with a side-by-side reconciliation against the legacy system. Auditor-ready, signed off, no surprises at year-end.

    Data migration is a technical exercise, but the design questions are upstream — what to migrate, what to archive, how to map the legacy chart of accounts to a redesigned Intacct chart, how to handle historic transactions, how to reconcile. We treat the migration as a project in its own right, with its own acceptance criteria, separate from the configuration work it feeds into.

    Scope

    What migrations engagements cover

    • 01

      From Pastel Partner / Evolution

      Trial balance, customers, suppliers, items, open AR/AP, and selected transactional history.

    • 02

      From Xero / QuickBooks

      Mapping cleanup, dimensional restructuring, and full historic load where it adds value.

    • 03

      From Sage 50 / 200 / X3

      Structural translation between Sage products that don't share a schema. We've seen the gotchas.

    • 04

      Fixed asset register

      Asset records, depreciation schedules, tax registers loaded and reconciled before go-live.

    • 05

      Project history (PSA)

      Projects, tasks, time, and billing history for Professional Services Automation customers.

    • 06

      Reconciliation + sign-off

      Every migration ends with side-by-side reconciliation. Auditor-friendly evidence pack on completion.

    Delivery method

    How a migration runs

    01

    Source extract

    Pull data from the legacy system via standard exports or direct database extracts. Document the source state.

    02

    Transform

    Map legacy GL codes to the redesigned Intacct chart of accounts. Apply dimensional tagging. Clean known data issues.

    03

    Load

    Load into Intacct via Smart Events, the Web Services API, or Sage Intacct's import utilities. Logged and verified.

    04

    Reconcile

    Side-by-side comparison against the legacy system. Differences identified, explained, fixed.

    05

    Sign-off

    Finance team and external auditor sign off the migration before cut-over.

    Why us

    Why this lands cleanly with Bo Gartner

    • We've migrated from every common SA legacy system. The pattern is known.
    • Reconciliation is built into the method, not added on at the end.
    • Historic data depth is a conversation — we right-size the migration scope to what actually adds value.
    • Auditor walkthrough on migration approach before extract starts.

    Common questions

    Frequently asked

    Most SA mid-market organisations migrate trial balance, master files, open AR/AP, fixed assets in detail, plus 1–3 years of historic transactional data for reporting continuity. Older history typically stays in an archived copy of the legacy system.

    Within an implementation engagement, migration overlaps with Configure (roughly weeks 5–8 of a 12-week project). Standalone migration engagements run 4–8 weeks depending on legacy system complexity and historic data depth.

    Yes — that is by design. Every migration produces a reconciliation pack: source extract, transformation mapping, load logs, and a side-by-side comparison signed off by your finance lead. We walk your external auditor through it during Validate.

    Open AR and AP migrate as individual outstanding items with their original invoice references, due dates, and ageing buckets. Customer and supplier statements continue from cut-over without losing the historical context.

    Ready to talk specifics?

    Tell us about your finance team's reality. We'll come back with an honest read on fit, timeline, and price within one business day.

    Book a consult