Pastel to Xero Migration Checklist
Follow this Pastel to Xero migration checklist to prepare balances, source records, VAT support, and workflows before moving your SME to the cloud.
- A safe migration starts by cleaning the Pastel source file before moving any data.
- The checklist should confirm cutoff date, opening balances, document storage, and workflow changes.
- Migration should not be used to hide unresolved bookkeeping problems.
- The first month after migration needs a closer review than a normal month-end.
Pastel to xero migration checklist matters most when the owner needs a straight answer quickly and the file cannot provide one. We see this in South African SMEs when opening balances, chart-of-accounts decisions, bank rules, and notes for overrides or exceptions is still incomplete and the next month-end or SARS request is already close.
A Pastel to Xero migration should make the bookkeeping cleaner, not just newer.
That means the checklist needs to focus on source quality before the software import.
The six migration checkpoints
1. Cutoff date
Decide the last month to be completed in Pastel and the first month to be controlled in Xero.
2. Source-file cleanup
Review unreconciled balances, duplicate records, unexplained journals, and open items before migration.
3. Opening-balance review
Confirm that the balances being moved are good enough to trust.
4. Document and schedule transfer
Make sure support schedules and source files are accessible in the new workflow.
5. Workflow redesign
Migration should change how the business collects documents, not only where the data sits.
6. First-month review
Treat the first Xero month as a stabilization month with extra reconciliation review.
A migration planning table
| Migration area | What to confirm |
|---|---|
| Cutoff | Last Pastel month and first Xero month agreed |
| Balances | Key accounts reviewed and explained |
| Open items | Old issues listed separately |
| Documents | Shared folder and support schedules available |
| Workflow | New document and approval process defined |
| Review | First-month review owner named |
If any row is vague, the migration is not ready.
The source-file checklist
Before anything moves:
- reconcile the bank as far as practical
- review supplier and customer ledgers
- identify old unexplained balances
- remove or explain repeated coding noise
- confirm the chart of accounts is still fit for purpose
This is the work that prevents a cloud migration from becoming a cloud cleanup.
The document-transfer checklist
| Support area | Transfer requirement |
|---|---|
| Bank statements | All current and recent periods available |
| Supplier invoices | Shared and traceable |
| Customer support | Easy to access if allocations are questioned |
| VAT schedules | Moved and clearly labeled |
Migration should improve traceability, not reduce it.
The workflow checklist
The most useful question is:
What will the business do differently once it is on Xero?
If the answer is "nothing", the migration may not solve much.
Define:
- who uploads documents
- who approves unusual items
- how bank-feed exceptions are handled
- how month-end will be closed
That is where the operational value comes from.
The first-month checklist
Once the business is live on Xero:
- review opening balances carefully
- test bank-feed behavior
- confirm coding patterns are consistent
- check whether the new workflow is actually being used
This is the month that proves whether the migration worked.
VAT and SARS records to protect during migration
For a South African SME, the migration must preserve the evidence behind VAT and income-tax records. The imported balances matter, but so do the working papers that explain how those balances were built.
Before the cutoff, keep copies of:
- VAT201 support schedules for recent filing periods
- input-tax support for material claims
- output VAT reports or sales summaries
- bank reconciliation reports for the final Pastel months
- customer and supplier age analyses at cutoff
- fixed-asset and loan schedules where they affect opening balances
Those records should not sit only inside the old Pastel file. Store them in a shared document folder with clear period labels so the business can answer later SARS or accountant questions without reopening the migration project.
Use the bookkeeping documents checklist with this step. It helps separate documents needed for monthly bookkeeping from evidence needed for review, audit, or SARS queries.
Opening balances that deserve extra review
Opening balances are where many migrations look clean at first and become expensive later. The import may balance technically while still carrying old issues into Xero.
Review these balances separately:
| Balance | Why it needs attention |
|---|---|
| Bank | A bank opening balance is only useful if the final Pastel reconciliation is clean |
| VAT | VAT control must agree to recent VAT201 support and open timing items |
| Trade receivables | Old customer balances should not be imported as if they are collectible |
| Trade payables | Supplier balances need statement support and dispute notes |
| Director loan | Owner transactions should be explained before they become Xero history |
| Suspense or clearing | These accounts should be cleared or documented before go-live |
If those balances are weak, migration should include a cleanup decision. Some items may be imported with notes, but they should not be hidden inside a new chart of accounts.
How to decide what should not be migrated
Not every Pastel problem deserves a permanent home in Xero. A practical migration plan should decide what gets moved, what gets summarized, and what gets parked as historical support.
Useful questions:
- Does the item affect a current balance that management still relies on?
- Does the business need transaction-level detail for SARS, customers, suppliers, or year-end?
- Is the old detail reliable enough to import without creating confusion?
- Can the issue be better handled through a documented adjustment and support schedule?
This is especially important for old customer balances, stale supplier credits, repeated suspense postings, and historical VAT differences. Importing everything may feel safe, but it can make the new Xero file harder to trust.
If the business is changing bookkeepers at the same time, use how to switch bookkeepers before the migration is finalized. The handover and migration should support each other, not create two separate versions of the truth.
Post-migration controls for the first quarter
The first month is the most obvious review point, but the first quarter is where deeper migration issues normally appear. The business should schedule a short review after each of the first three Xero month-ends.
Check whether:
- bank rules are creating consistent coding
- recurring supplier and customer allocations are behaving as expected
- VAT reports line up with the bookkeeping support
- old Pastel issues are being resolved rather than ignored
- management reports are easier to explain than before the move
If the same exception appears for more than one month, treat it as a process defect, not a one-off migration adjustment. That is where the Xero bookkeeping checklist becomes useful after the move.
Roles to assign before migration starts
A clean migration needs named owners. If every decision sits with the owner, the bookkeeper, the accountant, and the software adviser at the same time, the project slows down and weak choices get made by default.
Assign one owner for the cutoff date, one owner for source-file cleanup, one owner for opening-balance review, and one owner for the first-month Xero close. In a small SME, one person may hold more than one role, but the role should still be explicit.
Also decide who approves adjustments. Historical balances often need judgment. A bookkeeper can identify the problem, but management should approve material write-offs, director-loan corrections, old customer balances, or VAT adjustments that affect the final position.
The final migration file should include a short note showing what was imported, what was adjusted, and what was deliberately left as historical support. That note is useful when a future reviewer asks why the Xero file does not match a raw Pastel export line for line.
That note should be stored with the cutoff reports, not only in email.
Keep the note plain: cutoff period, balances reviewed, unresolved items, approvals, and where the support sits. That is enough for a future bookkeeper to understand the migration without reopening every old Pastel report.
When to delay the move
Delay if:
- the source balances are too weak to trust
- the business has no clean cutoff point
- document storage is still fragmented
- VAT or year-end deadlines are already too close
Moving at the wrong time creates more finance pressure than staying on Pastel one cycle longer and preparing properly.
Use this page with
- Pastel bookkeeping services
- Xero bookkeeping services
- Xero bookkeeping checklist
- can Xero replace a bookkeeper?
The goal is not merely to change software. The goal is to move into a cleaner bookkeeping process with fewer recurring balance problems.

