03 Migration
Moving off the old ledger, without losing the record
Our most common migration, and the one with the most folklore attached to it. What actually moves is smaller than people expect, and that is the point.
- Moves: item, customer and supplier masters after de-duplication, the chart of accounts remapped, opening balances as at the cutover date, open invoices and bills, and stock on hand with batch or serial detail where it is tracked.
- Stays behind: closed transaction history. The old file remains readable for as long as your statutory retention window runs, which is both cheaper and safer than reconstructing years of postings in a new schema.
- Never migrated blind: duplicate items, dormant ledgers, obsolete tax masters and accounts nobody can explain. A migration is the one moment when removing them costs nothing.
- Reconciled before sign-off: trial balance, stock value and receivables and payables agreed between the two systems as at the cutover date, in writing, before the old system is stood down.
We had run the old ledger for eleven years and assumed the migration would take all of it with us. It took the balances and the open items, and the old file is still there for anything older.
04 Statutory
Tax configuration and the audit trail
Zoho Books ships a country edition for the major indirect tax regimes, and it still has to be configured for your business. These are the settings a self-service setup most often misses.
| Area | What gets set | Tested against |
|---|---|---|
| Tax rates and masters | Rates, classification codes for goods and services, exempt and zero-rated flags | Twenty real documents from your last quarter |
| Jurisdiction rules | Which rate applies by customer, branch and destination | Actual invoices across every border you trade over |
| Reverse charge | The inward supplies attracting it, and the liability posting | Your existing reverse charge entries |
| E-invoicing | Network credentials, document types, and the acknowledgement flow | A live test document on the network |
| E-way bills | Thresholds, transporter details, generation from the invoice | A dispatch from your own warehouse |
| Audit trail | Edit log behaviour, and that it cannot be disabled | A documented verification before phase 1 |
- The audit trail requirement is not local to any one country: an unalterable, timestamped record of each entry and each later change is control A.8.15 of ISO/IEC 27001, and it is the first thing an external audit asks to see. We verify on your deployment that it cannot be switched off.
- Where your country mandates e-invoicing, each document leaves as a structured file on Peppol or the national network rather than as a PDF, and we test that path with a live document before go-live.
05 Delivery
The five steps
Licence first, data second, tax third. Configuring an app before the masters are clean is the most common way a Zoho rollout ends up rebuilt.
Step 1: Model the licence
Zoho One against individual apps on your real headcount and apps-per-role. You get the arithmetic, not a recommendation to take on trust.
2 to 3 daysStep 2: Clean and migrate the masters
De-duplication happens in the export, not after the import. Opening balances, open items and stock follow at the cutover date.
1 to 3 weeksStep 3: Configure the tax detail
Rates, jurisdiction rules, classification codes, reverse charge and e-invoicing, each tested against real documents from your last quarter.
1 to 2 weeksStep 4: Close the gaps in Creator
Job cards, checklists, field forms and approval flows built inside the same account, so they share masters instead of becoming a parallel system.
1 to 3 weeksStep 5: Train, cut over, hypercare
Training by role, a parallel period, then Books and Inventory live first with 30 days of hypercare before the next phase starts.
30 days per phase
06 The people
Who do you actually work with?
Four founders, named. IncorpX is a Zoho Authorized Partner, so the licence advice, the build and the training all come from the same team.
Nobody here is quoting someone else optimism. The people who recommend the app list are the people who have to make it work.
-
Dhanush Prabha
Co-Founder, CTO and CMO
Configures the workflows, roles and approvals, handles the imports, and reconciles the opening balances.
-
Sriram Ravichandran
Founder and CEO
Decides which apps you actually need, agrees the licence plan, and owns adoption after go-live.
-
-
07 Cross-border
How do we work with clients in another country?
None of this needs you to be in any particular country. The work is remote either way, so these are the answers a buyer asks for before signing, and they are the same on every engagement we run.
Working hours
Our day runs on UTC+5:30. The overlap window with your team is written into the scope rather than assumed, and everything outside it runs asynchronously.
How we communicate
One written update a day on the channel you already use, a standing weekly call inside the overlap window, and a named person to escalate to. Nothing important is agreed only on a call.
Who you contract with
Synerdyn Private Limited, the company behind IncorpX, named in the agreement with its registration number. The governing law and the forum are agreed before you sign, not after a dispute.
Currency and payment
Invoiced in your currency or in ours, your choice, and settled by bank transfer. Milestones are tied to deliverables you can see, never to elapsed time.
What you own
Copyright in everything built for you is assigned on final payment: source code, design files, prompts, configuration and documentation. Third-party licences are listed by name so nothing is a surprise later.
Where data sits
You choose the region your data is stored and processed in, and the answer is written down before the build starts, with who at IncorpX can reach it and for how long.
Offset from our working day standard time
- London-5:30
- Dubai-1:30
- Singapore+2:30
- Sydney+4:30
- New York-10:30
- San Francisco-13:30
IncorpX is a brand of Synerdyn Private Limited. The contracting entity, the governing law and the invoicing currency are all named in the proposal before you sign anything.
08 Reference
Terms used on this page
- Zoho One
- The bundled licence covering the suite on a per-employee basis, usually cheaper past three or four apps per user.
- Zoho Creator
- The low-code application platform inside the same account, used for job cards, checklists, field forms and approvals.
- Cutover date
- The date at which balances and open items are struck and the new system becomes the book of account.
- Jurisdiction rule
- The rule that decides which tax rate a line attracts, from where the supplier is, where the customer is and what is being supplied. Misconfigured more often than any other setting.
- Peppol
- The interoperability network most mandated e-invoicing regimes transmit on, used across much of Europe and in Singapore, Australia and New Zealand.
- Audit trail
- A non-erasable log of each transaction and each later change with its date. Control A.8.15 of ISO/IEC 27001, verified on your deployment rather than assumed.
- GDPR
- The EU and UK data protection regime. Article 83 sets administrative fines of up to €20 million or 4% of worldwide annual turnover, whichever is higher, which is why consent, retention and access control are build decisions here rather than paperwork.
09 Questions
Zoho implementation FAQs
Next step
Tell us your headcount and what you run today.
You get an app list, the Zoho One against individual apps arithmetic on your real numbers, a migration plan and a fixed quote. Usually within one working day.
Read by Dhanush Prabha, our CTO, not a form queue. Reply usually within one working day, in your time zone.
