Migration
We move your book. You keep working.
From your current platform to Finvica without a gap in service or a re-registration of your clients.
The commitment
Migration is part of the onboarding engagement — not a separate project you pay for twice.
Switching cost is the single largest objection in this category, and most vendors handle it by not mentioning it. The plan below is what the engagement actually looks like. Scope for your specific book is agreed on the call, because a book of three hundred clients and a book of thirty thousand are not the same job.
The plan
Ten working days, and who does what.
Discovery and export
We agree what is moving and you request the exports from your current platform. Most vendors will provide them; where one is obstructive we will tell you what to ask for by name.
Days 1–2 · you export, we specify
Data mapping and validation
Your fields are mapped to ours and validated for the things that quietly break later — duplicate folios, clients with no PAN, transactions with no matching holding.
Days 3–4 · we map, you answer questions
Trial import into a sandbox
Everything loads into a sandbox tenant that is yours to inspect. You look at your own clients, your own holdings and your own history before anything is live.
Day 5 · we import, you inspect
Corrections and re-import
You tell us what is wrong. It usually is, somewhere — this day exists because pretending otherwise is how migrations fail in week three rather than week one.
Days 6–7 · you review, we correct
Routing entity and RTA feeds
Credentials for your routing entity and RTA feeds are configured and tested against real files, so the connection is proven before your book depends on it.
Day 8 · we configure, you authorise
Parallel run
Both systems live at once. You work as normal and we reconcile the two at the end of the day. Nothing is switched off until the numbers agree.
Day 9 · both systems live
Cutover
You work in Finvica. Your old platform stays available read-only for as long as your contract with them runs.
Day 10 · you go live
What moves
What comes across.
Clients and hierarchy. Every client, with the group, family and account structure they sit in.
Folios and holdings. Current positions across every product class your export covers.
Transaction history and cost basis. The full record where your platform exports it — this is what makes capital gains reporting correct afterwards.
SIP and mandate registrations. Mapped rather than re-registered, so instalments continue uninterrupted.
Sub-broker mappings. Who is mapped to whom, and on what split.
Commission history. Where your current platform will export it.
What does not
What does not come across, and why.
Being specific here is worth more than a reassuring sentence, because you will find this out either way — the only question is whether you find it out from us or in week three.
CRM notes and task history rarely export from any platform in this category. If years of client conversation live in your current system, plan to keep read-only access rather than assume it moves.
Report templates and customisations do not transfer. Anything you have built up is rebuilt on our side, which is work but is also a chance to drop the templates nobody actually reads.
Commission history is the most commonly withheld export in the market. Some vendors provide it in full, some provide summaries, some make it difficult. We will tell you which you are dealing with as soon as we see what comes back.
Cost basis on very old positions is sometimes incomplete at source, particularly from spreadsheets. Where it is missing we will flag the gap rather than compute a plausible number, because a wrong cost basis surfaces as a wrong capital gains figure years later.
What comes across cleanly
Clients, folios, holdings and transaction history export in a structured form and map cleanly. SIP registrations carry across with their mandates intact.
Where it gets awkward
Commission history is often the hardest part to extract in full, and CRM notes and task history rarely export at all. Plan to keep read-only access for a period rather than assume everything moves.
What people ask before switching.
Do my clients have to re-register?
No. You keep your own ARN or RIA registration and your clients stay registered with you. The platform underneath changes; the relationship does not, and your clients need do nothing.
Do SIPs break?
No. Existing SIP registrations and their mandates are mapped across rather than cancelled and re-created, so instalments continue on schedule and nobody is asked to re-mandate.
What happens to my commission history?
It comes across where your current platform will export it, and we will tell you plainly if it will not. Historical brokerage matters for your own reconciliation, so this is worth pushing your incumbent on early.
Can I run both platforms in parallel?
Yes, and day nine of the plan above is exactly that. Nothing is switched off until the two agree, because a cutover you cannot verify is a cutover you cannot undo.
What if the data is wrong?
It usually is, somewhere. That is why the trial import lands in a sandbox you inspect before anything goes live, and why there is a correction cycle built into the plan rather than bolted on when it goes wrong.
Who does the work?
We do the mapping, the import and the reconciliation. You request the exports from your current vendor, answer questions about your own conventions, and check the result. Nobody can do those three things for you.
What does it cost?
Migration is part of the onboarding engagement rather than a separate line item, and the scope is agreed on the call.
What if we start and it does not work out?
You will know inside the sandbox stage, before anything touches your live book and before you have switched off anything you rely on. That is the point of ordering the plan this way.
Send us an export and we will tell you what we see.
Weekdays 09:30–18:30 IST