Glossary · Accounting & Bookkeeping
Historical Data Cut-off Date
Definition
A historical data cut-off date is the date, chosen in a software migration, up to which old transactions are carried into the new system only as summarised opening balances. Transactions after that date are recorded in full in the new system. The date is fixed at the start of the project and decides how much detailed history is re-created.
At a glance
- Category
- Accounting & Bookkeeping
- In this entry
- What it means for Indian businesses How it works · Example
In practice
01 What it means for Indian businesses
Every move from one accounting system to another, such as Tally to Zoho Books or Odoo, needs a cut-off date. Before it, the old system keeps the detail. At it, the closing balances of the old system (ledgers, debtors, creditors and stock) become the opening balances of the new one.
The cut-off date and the go-live date are related but different. The cut-off date is the last day of old data, such as 31 March. The go-live date is the first day of new entries, such as 1 April. A parallel run can leave a gap between the two.
Most businesses pick the last day of a financial year, so the opening balances tie to the audited balance sheet and to the year's filed GST and TDS returns. A quarter or month end works if a mid-year switch cannot wait. A mid-month date forces every open invoice to be split by hand.
Data not migrated is not thrown away. The old books must still be kept for the period the law requires (for a company, at least eight financial years under section 128(5) of the Companies Act 2013).
How it works
02 How it works
- Choose the date
Usually a year, quarter or month end that is already closed, reconciled and filed.
- Freeze the old system
Up to that date.
- Extract balances
As at the date.
- Load them as opening balances
In the new system.
- Go live
From the next day, record all new transactions only in the new system.
- Archive the old records
For the retention period.
Whatever the software, the opening balances must equal the old system's closing balances at the cut-off date.
Worked example
03 Example
An example, not advice on your facts.
A manufacturer moves to new software. It sets 31 March 2026 as the cut-off date and 1 April 2026 as go-live.
| Step | Date | Amount (₹) |
|---|---|---|
| Old system closed and reconciled | 31 Mar 2026 | — |
| Debtors per old system | 31 Mar 2026 | 18,00,000 |
| Debtors opening balance in new system | 1 Apr 2026 | 18,00,000 (must match) |
| New sales and receipts | From 1 Apr 2026 | Recorded only in the new system |
Watch out
04 Common mistakes
- Opening balances that do not match the old closing balances.
- Entering transactions dated before the cut-off in the new system, which double-counts them against the opening balances.
- Choosing a mid-period date that complicates the first returns and reconciliations.
- Deleting old data because it was not migrated.
Need help with a historical data cut-off date? See our Migration: Tally to Zoho Books or Migration: Tally to Odoo. You can also see our Catch-Up Bookkeeping Services for Backlogged Books.
Review and sources
Sources: Companies Act, 2013 (India Code consolidated text, Nov 2024) s.128
