Migrating from Pastel, Sage 50, or QuickBooks to Sage Intacct: a 90-day plan

For most South African mid-market organisations, the path to Sage Intacct starts in Pastel Partner or Pastel Evolution, sometimes in Sage 50 or Sage 200, increasingly often in QuickBooks Online or Xero. The decision to migrate usually arrives when the organisation has outgrown the system in three or four specific ways at once: multi-entity has become unmanageable, reporting requires spreadsheet acrobatics, the audit is painful, and integration with other business systems is non-existent.

This is the 90-day migration plan Bo Gartner runs for these engagements, under our Intacct Activation method.

Phase 1 — Discover (weeks 1–2)

The Discover phase decides whether the project will succeed. We map:

• Current state: which legacy system, which version, what's in it (chart of accounts, customer/supplier counts, transaction volumes, history depth), what works, what doesn't.
• Target chart of accounts: not a copy of the old COA; a redesign that uses Sage Intacct's dimensional model properly.
• Dimensions: entity, location, department, project, B-BBEE category, segment.
• Integrations: payroll, banking, CRM, payment gateways.
• Migration scope: trial balance, customers, suppliers, items, open AR/AP, fixed assets, historic transactions (how many years).
• Audit posture: external auditor walkthrough; controls expectations.
• Cut-over date: typically a quarter or year boundary, with the cut-over weekend planned 60 days out.

Discover ends with a fixed-price proposal, a signed scope, and a project timeline. No surprises after this point.

Phase 2 — Configure (weeks 3–6)

Configure builds Sage Intacct in your own environment — not a sandbox — to the design from Discover. Multi-entity structure, chart of accounts, dimensions, VAT codes, approval workflows, AP automation rules, AR billing rules, reporting templates, dashboards. Integrations are scoped and the build begins in parallel.

By the end of Configure, the system is operational. The finance team is invited in to drive it, identify gaps, and refine workflows.

Phase 3 — Migrate (weeks 5–8, overlapping)

Migration is where most of the technical work lives. We extract from the legacy system, transform to Sage Intacct's format, and load via the Web Services API or Smart Events. The migration covers:

• Trial balance as at cut-over.
• Customer master file.
• Supplier master file.
• Item master (for inventory).
• Open AR balances (with original invoice references).
• Open AP balances.
• Fixed asset register (assets, depreciation schedules, tax registers).
• Historic transactions (typically 1–3 years).

Each batch is reconciled against the legacy system and signed off by the finance team before the next batch loads. By the end of migration, Sage Intacct holds a complete, reconciled picture as at cut-over.

Phase 4 — Validate (weeks 9–11)

Parallel run is non-negotiable. For one full period — usually a month — the finance team runs month-end in both the legacy system and Sage Intacct. Reconciliation differences are identified, explained, and either fixed in configuration or accepted with documentation. The auditor reviews. The CFO signs off.

UAT runs in parallel: every workflow tested by the user who will own it in production. AP capture and approval. AR invoicing and collection. Bank reconciliation. Month-end close. Consolidated reporting. Each tested, documented, signed off.

Phase 5 — Cut-over (one weekend)

Cut-over is a Friday-evening-to-Monday-morning operation. Final balances from the legacy system are taken; final adjustments are posted; the legacy system is locked. Sage Intacct opening balances are confirmed. Production access is enabled for users. The Monday morning team meeting briefs everyone on the new system, the support channels, and the cut-over status.

Most cut-overs go quietly. The ones that do not are the ones where validation was skipped.

Phase 6 — Hypercare (weeks 12–24)

Ninety days of hypercare follow go-live. We're in the room (or on the call) for the first close, the first VAT 201 submission, the first audit query, the first 'why isn't this report showing what I expect?' moment. Daily standups for the first two weeks; weekly thereafter. By the end of hypercare, the finance team owns the platform.

Where the work actually lives

People over-index on data migration as the hard part. It is technically demanding, but the harder questions are upstream: getting the chart of accounts right, getting the dimensional model right, getting the integrations right. A perfect data migration into a wrongly-designed Intacct environment is wasted work; an imperfect data migration into a well-designed Intacct environment can be cleaned up over the first ninety days.

That is why Bo Gartner spends two structured weeks in Discover before anyone touches data. Book a consult if you're looking at a Pastel-to-Intacct migration and want a fixed-price, predictable engagement.