Home / Switch
Switching · CanadaMove to FigsFlow without pausing the work
Changing practice management software should not cost a Canadian firm a month of billable time. You get one named migration lead, a plan dated against your own deadlines, and both systems running side by side until you decide to switch the old one off.
- Who runs it
- One named lead
- Your old system
- Stays live alongside
- Your documents
- Stay in SharePoint
- Discovery callPlan written against your own deadlinesDone
- ConfigurationTemplates, pricing rules and clause sets builtDone
- Data and documentsRecords imported · files stay in SharePointIn progress
- Go live and supportBoth systems running side by sideScheduled
Illustrative plan. Firm name and timings are sample data.
Why firms stall
Three things stop firms moving. None of them has to.
Nobody puts off a switch because the software is wrong. They put it off because of what the move itself might cost. Here is what actually happens to each one.
“We will lose a month to re-keying client data.”
What actually happens
Client and contact records come across in a structured import, checked against your old system before anyone relies on them. Documents are not re-keyed at all — they stay in your SharePoint and FigsFlow points at them.
Imported, then reconciled with you
“My team will be learning software in the middle of the season.”
What actually happens
Configuration happens before anyone logs in. Your workflow templates, pricing rules, clause sets and team structure are built first, so the first screen your team sees already looks like your firm.
Built first, opened second
“Something will break and nobody will pick up.”
What actually happens
You get one named migration lead on a direct line for the first month, not a ticket queue and not a different name each time. The old system stays available until you decide otherwise.
One person, start to finish

Week two · configuration reviewHarbourview Accounting
Who you get
One person owns your move, first call to last job.
Not a handover chain, and not a shared inbox. The same migration lead runs your discovery call, builds your configuration, sits with you while the first imported records are checked, and is still there the week after you go live.
- 01Writes the plan against your calendarYour immovable deadlines go in first. Everything else is arranged around them.
- 02Builds the configuration before anyone logs inWorkflows, pricing rules, clause sets and team structure, ready for you to review.
- 03Checks the first live jobs with your teamSide by side, on real work, not a sandbox.
- 04Answers directly for the first monthOne name, one number, no queue position.
Clause sets, risk ratings and filings stay with your firm. FigsFlow supplies the workflow and the evidence trail; the professional judgement is yours.
How the switch works
Four steps. Your pace.
Some firms switch over a weekend. Others run both systems for a month and move new work across first. The steps are the same either way — only the spacing between them changes.
Step 01
Discovery call
We learn how the firm works today: which tools you are leaving, which processes are yours and not negotiable, and which deadlines cannot move. You leave with a dated plan.
Step 02
Configuration
Your workflow templates, pricing rules, engagement letter clause sets and team structure are built in FigsFlow before anything goes live. You review it before your team ever sees it.
Step 03
Data and documents
Client records move across in a structured import and are reconciled against your old system. Documents stay in your SharePoint — FigsFlow points at them, it does not copy them into a second store.
Step 04
Go live and support
Your team starts working in FigsFlow with hands-on help from someone who has done this before. The old system stays available as long as you want it. No ticket queue for the first month.
Mid-season move? It is done more often than you would think. Configure first, go live on new work only, and leave the jobs already in flight where they are until the season closes.
Talk it through on a callWhat actually moves
Some things come with you. Some things should not move at all.
A switch goes wrong when a vendor insists on owning everything. FigsFlow takes the practice management and leaves the rest of your stack where your firm already trusts it.
Comes across with you
Imported and reconciled- Client and contact recordsImported in a structured pass, then checked against the system you are leaving before anyone relies on them.
- Jobs and recurring workRebuilt on your own workflow templates, with the right owner and the right review stage on each.
- Engagement letters and clause setsLoaded ready for a partner at your firm to read and approve. Nothing is published on your behalf.
- Pricing rules and fee schedulesSet in CAD, so a quote reads correctly the first time somebody raises one.
- Your team and their permissionsWho sees what, who approves what, and which partner signs off which work.
Stays exactly where it is
Untouched by the move- Documents, in your SharePointFigsFlow points at the folder structure you already have. Your files are not copied into a second store.
- Email, in OutlookThreads link to the client record. The mailbox, the retention policy and the archive stay yours.
- Your ledger, wherever it livesFigsFlow is practice management. It runs the firm, not the books.
- Professional judgementFigsFlow drafts, records and evidences the work. It does not advise, and it does not file with the CRA or FINTRAC on your behalf.
The honest test
Bring the client that worries you most.
The one with the trust, the holding company and the fee that crept. If that client runs cleanly on one record in the demo, the rest of the book will follow. If it does not, you will have found out in forty-five minutes rather than four months.
- 01Set that client up liveOn your structure and your numbers, while you watch. Not a sample file, and not a recording.
- 02Price the work in front of youYour own pricing rules, applied to the job as it actually is, so you can see where the fee should have landed.
- 03Read the letter it producesThe engagement letter that comes out the other end, for a partner at your firm to review and approve.

First call · about 45 minutes
What firms ask before they move
Start here
One call, and a plan you keep either way.
Pick a time that sits away from your own deadlines. You leave with a dated plan written around them, whether or not your firm decides to move.
Nothing moves until your firm says go
What happens after you book
- A call, not a pitch deckWe work from the workflow you run today and the files you actually open, not a demo script.
- A dated plan you can take to your partnersWritten around your immovable deadlines, with the switching support that is included spelled out.
- A decision that is still yoursNo configuration starts, and no records move, until your firm says go.


