Switching
How to switch practice software without losing a filing
Most firms know their current setup is holding them back long before they move. What stops them is the fear of changing over in the middle of the year and dropping a deadline in the gap. The fear is reasonable. It is also manageable, because the work that matters on a cut-over is a short list.
This guide is a practice management migration plan: what to move and what to leave, how to pick the window from the real GST, income-tax and MCA calendar for November 2026 to March 2027, how to run old and new side by side for one cycle, and what to check afterwards. The T4Suite parts describe what its spreadsheet import actually accepts and refuses.
Practice management migration: what to move, and what not to
Not everything in the old system needs to come across. Some of it is live work that must be there on day one. Some is history that is safe to keep where it is. Sort it into three piles before you touch a file.
| What | Move it? | How it comes into T4Suite |
|---|---|---|
| Entities (the firm's own LLP, firm or company) | Yes, first | Set up by hand, with GSTIN and bank details. The import does not create them; a row that names an entity not yet there is refused |
| Services and sub-heads | Yes | Import: Group, Service, Service Hours, Sub-head, Sub-head Hours |
| Team | Yes | Import: Name, Email, Role, with Phone, Entity and annual CTC optional. Each person is invited by link |
| Clients | Yes | Import: Name and Org Type, with PAN, GST registered, GSTIN and Entities optional |
| Open tasks and this year's filings | Yes | Import: Service, Client, Entity and Financial year, with Due, Priority, With and Fee optional. They arrive as drafts |
| Recurring filings (GSTR-1, GSTR-3B, TDS) | Rebuild | Not in the import. Set each up once as a recurring series, then check the calendar against your own filing list |
| Unbilled work | Yes, as a fee on the task | Put the agreed fee in the task's Fee column. Bills come from a completed job's costing; there are no standalone bills |
| Outstanding bills and receipts | No | The import has no bills. Keep the old system for collecting them, read-only, until they are paid |
| Documents and old working papers | Only the live ones | Not part of the import. Attach what the open tasks need and archive the rest |
The line to hold is this: move what drives next month's work, not what records last year's. A firm that tries to carry every old invoice and paper across delays the cut-over by weeks, and gains nothing on a filing day.
Pick the window from the real calendar
The best time to switch is the gap between two filing peaks, and you can read it off the calendar. The dates below run from November 2026 to March 2027 for a monthly GST filer with a 31 March year end. GSTR-1 is due on the 11th and GSTR-3B on the 20th (the GST portal's GSTR-1 FAQ; rule 61(1) of the CGST Rules). Quarterly filers on QRMP file GSTR-1 on the 13th and GSTR-3B on the 22nd or the 24th of the month after the quarter (rule 61(1)(ii)). The income-tax and company dates are those read from CBDT Circular 07/2026 of 28 September 2026 and MCA General Circular 05/2026 of 24 October 2026, as set out in our compliance calendar guide on 8 November 2026.
| Date | Day | What falls due |
|---|---|---|
| 11 and 20 Nov 2026 | Wed, Fri | GSTR-1 and GSTR-3B for October |
| 21 Nov 2026 | Sat | Income-tax return for audited assessees and companies (extended by Circular 07/2026) |
| 30 Nov 2026 | Mon | Return where a transfer pricing report is required |
| 11 Dec 2026 | Fri | GSTR-1 for November |
| 15 Dec 2026 | Tue | Advance tax, at least 75 per cent |
| 20 Dec 2026 | Sun | GSTR-3B for November |
| 31 Dec 2026 | Thu | GSTR-9 and 9C for FY 2025-26; no-fee limit for AOC-4 |
| 11, 13, 20 Jan 2027 | Mon, Wed, Wed | GSTR-1 (monthly), GSTR-1 (QRMP, Oct to Dec), GSTR-3B (monthly) |
| 22 and 24 Jan 2027 | Fri, Sun | GSTR-3B for QRMP filers, by state group |
| 31 Jan 2027 | Sun | TDS statements for October to December; no-fee limit for MGT-7 |
| 11 and 20 Feb 2027 | Thu, Sat | GSTR-1 and GSTR-3B for January |
| 11 and 20 Mar 2027 | Thu, Sat | GSTR-1 and GSTR-3B for February |
| 15 Mar 2027 | Mon | Advance tax, the whole amount |
| 31 Mar 2027 | Wed | Year end |
Read the gaps. November is crowded by the 21st and the 30th. Late December is cut by the 31 December filings. March is the year end. That leaves the stretch after 31 January. Switch on Monday 1 February 2027, and the old and new systems then share one full monthly GST cycle: GSTR-1 on Thursday 11 February and GSTR-3B on Saturday 20 February. File the second by Friday 19 February. Retire the old system on Monday 22 February, ahead of the March peak.
If your firm cannot wait, the second-best window is 21 December 2026 to 10 January 2027. It works only if the 31 December filings are done first, and you stay out of the file store on those days.
The sequence, week by week
For a 1 February switch, a workable order is this. In the week of 25 January, export from the old system and clean the file: one row per client, a GSTIN on every registered client, one spelling per client name. On Saturday 30 January, create the entities, then import services, team, clients and tasks, in that order, because each needs the one before it. On Monday 1 February, the team starts logging new work in T4Suite and nothing new goes into the old system.
From the cut-over day, new work goes into T4Suite only. The old system stays available as your reference and for collecting old bills, but it takes no new tasks. The mistake is leaving both open for new work, so that one client's task exists twice and nobody knows which is live.
Run one cycle in parallel
Do not cut over cold. For three weeks, the old system stays your reference, while the team does the live work in T4Suite. Compare the two on the days that count: the GSTR-1 date of 11 February and the GSTR-3B date of 20 February. If T4Suite's calendar shows the same clients due on the same days as your old list, you have proved the recurring series. If it does not, you found the gap in February, not on 20 March.
A GST return is not the only thing to compare. Raise one real invoice in each entity before the end of the parallel period, so the invoice series, the GSTIN and the bank details have been used once on a real bill. The invoice number needs care. Rule 46(b) of the CGST Rules wants a consecutive serial number, in "one or multiple series", unique for the financial year. Give each entity a new series in T4Suite with its own prefix, and let the old system finish its own series, so the two never share a number.
What the T4Suite import takes and refuses
The import reads the first sheet of an .xlsx file, with the header in row 1. You download the template for each kind from the app, and the columns are read by their heading, not their position, so a file with columns in an older order still reads correctly. A file is capped at 5 MB. The import is a web feature, not on the phone.
A file is read before anything is added. The first pass decides what each row would do and writes nothing: add it, skip it because it is already there, or refuse it with the reason. You see that list, and only pressing Add adds. A refused row never holds up a good one.
Duplicates are skipped, not overwritten: a client by name, a team member by email, a service by group and name, and a task by service, client, entity and financial year. A name listed twice in one file is added once. This makes it safe to run the same file again after a fix.
Examples of what it refuses: a client row with no Name or Org Type; an Entities cell naming an entity that does not exist; a GSTIN that fails the check; a row that says GST registered is No but gives a GSTIN; a team row whose Role does not exist; a task whose service or client is not yet imported, whose financial year is not written like 2026-27, or whose Due is not a date; a Fee from someone who may not set fees. Dates are read day first.
What it does not take: recurring series, bills and receipts, time logs, notices and documents. T4Suite does not track UDIN, so there is nothing to import for it either.
Checks after the cut-over
Do these in the first two days, and write the results down.
Count: rows in each file against the records in the app, with skipped and refused rows accounted for. Sample: open ten clients, including the awkward ones, and compare GSTIN, PAN and entity with the old record. Per person: each team member's open tasks against the list the old system gave them on 29 January. Calendar: the next sixty days of due dates against your own filing list, client by client. First bill: one invoice from each entity, with the right number, GSTIN and bank account. Access: someone with a restricted role signs in and sees only what they should.
In T4Suite, everyone on a task is reminded in the app a week before it is due and again the day before. Check that the people on the imported tasks are the right ones, because the reminders go to them.
Bring the team along, not just the data
Software switches fail on adoption, not on data. The staff who log hours and update task status must find the new tool easier than the old habit, or they quietly keep the old one. Show each person their own open tasks in the new system on day one, and fix their first complaint the same day.