A clean migration from Excel working papers to a new audit platform rests on three decisions made before any file is uploaded: which prior-year figures and schedules must carry forward exactly (opening balances, prior-year comparatives, unresolved points carried forward), which content should be deliberately re-created inside the new system's structure rather than copy-pasted (risk assessments, control narratives, and checklists that should follow the new platform's format from day one), and how the migration itself gets documented so a reviewer or inspector can see why this year's working papers look structurally different from last year's.
Step 1: inventory what actually needs to move
- Opening balances and prior-year comparative figures for every schedule — these must tie out exactly, with no rounding drift introduced by the migration itself.
- Unresolved points carried forward from the prior year's file — a qualification, a management point, an unadjusted error noted for next year's attention.
- Fixed asset registers and depreciation schedules with multi-year history, since recreating these from scratch risks introducing errors in opening WDV.
- Related party relationships and balances that need year-on-year continuity to be checked.
Step 2: decide what to re-create instead of migrate
Some content is worth rebuilding in the new system's own structure rather than preserved as-is, because preserving it exactly would just carry the old system's weaknesses into the new one.
| Content | Migrate exactly, or rebuild? | Why |
|---|---|---|
| Opening balances / comparatives | Migrate exactly | Must tie out; no room for drift |
| Risk assessment and materiality workings | Rebuild in the new template | These should follow the new platform's structure and logic from year one, not carry over an old format bolted onto a new tool |
| Checklists and standard procedures | Rebuild using the platform's own templates | Re-keying old checklists as static text loses the benefit of a system that can actually track completion |
| Supporting schedules with multi-year history (fixed assets, provisions) | Migrate the historical figures, rebuild the current-year workings | History needs to survive; this year's method should use the new system properly |
Step 3: reconcile before and after the migration, not just once
- 01Tie the migrated opening balances to the prior year's signed-off closing figuresBefore relying on the new file for anything, confirm every opening balance matches the prior year's final, reviewed figures exactly.
- 02Spot-check a sample of migrated schedules against the original Excel sourceDon't assume an import ran cleanly just because it completed without an error message — check a sample by hand.
- 03Have someone other than the person who ran the migration review the reconciliationThe person who built the import is the least likely to notice their own mapping error.
Step 4: document the switch itself
A reviewer or quality control inspector looking at this year's file next to last year's will notice the structural change. A short note in the current file explaining when the firm switched systems, what was migrated versus rebuilt, and how the opening balances were reconciled answers the question before it's asked.
Regulatory requirement
Statutory retention requirements for audit working papers do not pause for a system migration. Confirm the prior-year Excel files remain retrievable and readable on their own for the full retention period, independent of whether the firm keeps using the old system.
A migration that happens mid-engagement, rather than between engagements, is a known way to lose track of which version of a schedule is authoritative. Where possible, migrate a client's file at the start of a new year's engagement, not partway through the current one.
Common practice, not a requirement
Running the migration on one or two clients first, rather than the whole portfolio at once, surfaces mapping problems while the stakes are still low — see the companion article on piloting on one client versus a firm-wide rollout.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- Technology, data & AI in auditMigrating from Excel working papers to audit softwareWhat a firm actually gains and loses leaving Excel, the version chaos Excel creates across a review chain, and a realistic first-engagement timeline.
- Audit workflow & automationA realistic 90-day audit automation rollout plan for a mid-size firmThirty days to set up, thirty to pilot on one or two clients, thirty to expand with lessons already applied — not a single big-bang switch in week one.
- Audit workflow & automationThe hidden costs of staying on a pure-Excel audit workflowExcel doesn't send an invoice, so the cost looks like zero. The real cost shows up two or three years in, in ways that are easy to miss until they happen.
- Audit workflow & automationPilot on one client or roll out firm-wide: a decision frameworkThe right rollout speed depends on how similar the firm's engagements actually are to each other, not on how confident the partner feels after the demo.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- GSTR-2B reconcilerMatches your purchase register against GSTR-2B — missing invoices either side, amount mismatches.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.