Somewhere in your office there is probably a machine that must never be switched off. It runs Pastel, it has run Pastel since before some of your staff matriculated, and an uncomfortable amount of your business history lives inside it. Every year thousands of South African businesses decide to retire that machine and move their books to the cloud, and every year a predictable fraction of those migrations go wrong in predictable ways: balances that do not balance, VAT periods that will not reconcile, staff who quietly keep a spreadsheet on the side because nobody taught them the new system.
None of those failures are caused by the software. They are caused by treating a migration as an IT task instead of what it really is: a financial project with a hard compliance deadline attached. This guide is the playbook we have watched succeed across dozens of conversions, written for the owner, financial manager or bookkeeper who will carry the responsibility. It assumes you are moving from Sage 50cloud Pastel or an older Pastel version, and it applies with minor adjustments to any desktop to cloud move.
First, confirm you should actually move
The honest first step is deciding whether migration serves the business or just the zeitgeist. The move makes clear sense when the drivers are structural: the server is dying and replacement money would fund years of subscriptions, the team went hybrid and remote desktop is a daily tax, the accountant charges for the backup file dance, or the business simply no longer needs the depth it is paying to maintain. The move deserves hesitation when Pastel is doing real work: heavy document volume, serial number stock, five companies on one licence, point of sale at the counter. Those shapes belong on desktop software or on a proper mid market system like Sage 200 Evolution, not on entry level cloud plans.
A useful test: list every Pastel module and report your business touched in the last quarter, then check the list against the cloud product's feature page. If more than two items have no equivalent, you are not migrating, you are downgrading, and the workarounds will eat the savings.
Choose the destination before the route
For most Pastel businesses the natural destination is Sage Accounting, and not out of brand loyalty: the chart of accounts concepts carry across, the VAT201 workflow is familiar, most SA practices know both products, and Sage provides an official conversion path. The genuine alternatives are QuickBooks Online, which rewards businesses that want deeper reporting and projects, and Xero, beloved of practices that have standardised on it. Locally, Palladium deserves a look from stock heavy businesses that want SQL depth without ERP money.
Pick one, take its trial, and rebuild a sample of your real world in it: your ten most complicated customers, your five weirdest recurring transactions, one full VAT cycle on paper. The trial month is your cheapest insurance and almost nobody uses it properly.
Timing: the calendar does half the work
Migration timing has a right answer and it is worth fighting for. The gold standard is your financial year end: opening balances are clean, comparatives live entirely in the old system, and the audit file has no seam running through it. The silver standard is any VAT period boundary, because the one seam you must never create is a VAT period split across two systems; reconciling half a VAT201 from each side is the single most common migration disaster we see.
Avoid February and March if payroll year end touches the same team, avoid your industry's peak season, and avoid the fortnight before any SARS deadline. Block out six to eight weeks from decision to completed first month, even though the conversion itself takes days; the calendar padding absorbs the surprises that always come.
The data decision: what moves and what stays
Here is the counsel that saves the most pain: do not try to move everything. Master data moves: customers, suppliers, items, and their balances. Opening balances move: the trial balance as at cutover, aged debtors and creditors item by item, bank balances to the cent, and VAT control accounts that tie to your last return. Open documents move: unpaid invoices, unallocated receipts, outstanding orders.
History mostly should not move. SARS requires five years of records, but it does not require them inside your new software. The old Pastel installation, or even a licensed read only copy on one machine, satisfies retention perfectly, and PDF exports of key reports per year belong in your document archive regardless. Businesses that insist on importing years of transactional history double their project cost and triple their reconciliation surface, for the privilege of clutter. Let history rest where it happened.
Before extracting anything, spring clean the old system: write off the debtors you will never collect, deactivate the customer duplicates accumulated since 2011, count the stock properly, and resolve the suspense account that everyone stopped mentioning. Migrating mess produces organised mess, and cleanup is cheaper on the familiar side.
The cutover fortnight, step by step
A clean cutover follows a rhythm. Close the final period in Pastel completely: every bank reconciled, every VAT figure tied to the last return filed, a full backup taken and tested, and a printed or PDF trial balance signed off by whoever owns the numbers. That signed trial balance is your source of truth for the next step, and disagreements later get settled against it.
Then build the new file: company details, VAT settings at 15% with your filing periods, financial year, users with sensible permissions, and bank feeds connected and confirmed flowing. Import master data and check samples by hand, ten customers, ten suppliers, twenty items, because import tools are good and not perfect. Capture opening balances from the signed trial balance, then prove them: the new system's aged debtors must equal the old one's to the cent, creditors likewise, bank likewise. Print both, staple them together, file them. Auditors love this artifact and so will you.
Only then does live processing begin, and the golden rule of the first month is one system per document: every new invoice, every payment, every capture happens in the cloud, no exceptions, while the old system stays read only. Half in, half out is how businesses lose invoices and minds.
Parallel running: cheap insurance, briefly
For businesses with volume, one parallel month, processing everything in both systems, buys certainty at the price of doubled capture. For a five person services firm it is overkill; for a thirty person trading business it is worth every duplicated keystroke. If a full parallel is too heavy, parallel the bank reconciliation and the VAT report alone: those two documents catch ninety percent of setup errors, from wrong VAT codes on items to a missing opening balance. End the parallel deliberately after one clean month; perpetual parallel running is a symptom of fear, not diligence.
People: the part that actually fails
Software migrations fail at the keyboard, not the database. The bookkeeper who has driven Pastel by muscle memory for fifteen years experiences the cloud product as a demotion to beginner, and unmanaged, that experience becomes resistance, and resistance becomes the shadow spreadsheet. Manage it directly: involve the daily users in the destination choice, pay for structured training rather than assuming intuition, and give the first month a lighter capture load where possible. Appoint one internal owner for questions, someone who did the training twice, so frustration has a friendly first stop before it becomes a support ticket or a grievance.
And communicate to the outside: your accountant needs access setup before cutover, not after; customers keep paying into the same bank account but statements will look different; suppliers may need to resend anything emailed to a capture address. A one paragraph note to each audience prevents a month of small confusions.
The first VAT return on the new system
Treat the first cloud VAT201 as a test you set for yourself. Run the report early, a week before the deadline. Tie its opening position to the closing position of the last desktop return. Check a sample of transactions at each rate, standard, zero and exempt, against source documents. If anything disagrees, the cause is almost always an item or customer imported with the wrong VAT setting, and fixing it in week one costs minutes. When this return reconciles cleanly, your migration is genuinely done; frame the moment however you see fit.
Who to hire, and what good help looks like
Most businesses should not migrate alone, and the market of helpers has three tiers. Your own accounting practice is the first stop: most SA practices have converted dozens of Pastel clients, they know your books already, and their fixed fee usually includes the opening balance proof and the first VAT return review. Sage business partners and certified consultants are the second tier, worth engaging when volume or modules complicate the extraction; ask specifically how many Pastel to cloud conversions they completed in the last year and request two references you may actually phone. Freelance bookkeepers advertising migration services are the third tier, sometimes excellent and sometimes learning on your data; the reference question filters them quickly. Whoever you choose, insist on three deliverables in writing: a signed opening balance reconciliation, a documented cutover date with a rollback plan, and one month of post go live support included. Good helpers offer these before you ask; hesitation on any of the three is your cue to keep looking.
Month two and beyond: making the cloud pay
The migration ends when the first VAT return reconciles, but the payoff compounds afterwards, and month two is when to collect it. Switch on the automations you were too busy for during cutover: recurring invoices for every retainer client, bank rules for every regular debit order, automatic statement runs and payment reminders. Give your accountant their own login and renegotiate the monthly fee now that the backup file dance is gone; several of our readers report meaningful reductions. Retire the old infrastructure deliberately, cancel the backup subscription, repurpose the server, and put a fraction of the saving into a proper LTE failover so load shedding never interrupts invoicing again. And diarise a one hour review after quarter one: which workarounds did the team invent, and does each one signal a missing setting, a missing module or a training gap? The businesses that extract full value from the cloud are not the ones that migrated perfectly; they are the ones that kept adjusting for ninety days afterwards.
Costs, honestly stated
Budget beyond the subscription: a practice or consultant assisted conversion typically runs a fixed fee worth every rand, training costs a day or two of productivity, and the parallel month costs capture time. Against that, retire the server replacement, the IT support retainer hours, the backup software and the annual desktop licence, and the arithmetic usually turns positive within the first year, before counting the hours the bank feeds return to the business every month. The cheapest migration is the one done once, properly.
The short version
A migration succeeds on preparation, timing and people, in that order, and the software is rarely the constraint. Move for structural reasons, not fashion. Choose the destination with your real workload, on trial, before committing. Cut over at a year end or VAT boundary, move balances and open items rather than history, prove the numbers with stapled reports, run one careful month, and train the humans like the project depends on them, because it does. Thousands of South African businesses make this move cleanly every year, and the difference between their experience and the horror stories is nothing more than the playbook above, followed patiently.
When you are ready to choose a destination, our verified reviews from South African businesses are the evidence base: start with the Sage Accounting profile, compare it against staying on Pastel, and take the shortlist to your accountant with this guide under your arm.
