Skip to main content
FigsFlow is coming to Canada 🍁 Launching January 2027 🇨🇦 Built for Canadian accounting firms
Figs Flow Canada

Home  /  Switch

Switching · Canada

Move 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

G2 reviewsVerified reviews

Switch plan · Harbourview AccountingWeek 3 of 6
62%
  1. Discovery callPlan written against your own deadlines
    Done
  2. ConfigurationTemplates, pricing rules and clause sets built
    Done
  3. Data and documentsRecords imported · files stay in SharePoint
    In progress
  4. Go live and supportBoth systems running side by side
    Scheduled
Named migration leadDirect line
Documents moved out of SharePointNone

Illustrative plan. Firm name and timings are sample data.

The group

Built by the people who run practices, not just software.

  • Taxule
  • Ledgian
  • Sterling Wells
  • UK Property Accountants
  • Property SPV

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

A FigsFlow migration lead and a firm’s practice manager working through a switch plan together at an office table

Week two · configuration reviewHarbourview Accounting

A direct line, not a queueYour migration lead stays reachable through the first month on FigsFlow.

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.

About 45 minutesDated 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.

We buildYou approve

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.

Structured importFiles stay put

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.

Side by sideDirect line

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 call

What 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.
A FigsFlow migration lead at her desk by the window, taking a first call with a Canadian firm about moving across

First call · about 45 minutes

Your call, your calendarPick a time that sits well away from your own deadlines.

What firms ask before they move

How long does a switch actually take?

Most firms run the four steps over two to six weeks. The variable is configuration, not the import — a firm with one workflow moves faster than a firm with eleven. Your migration lead dates the plan on the discovery call so you know before you commit.

Can we run both systems at the same time?

Yes, and many firms do. A common pattern is to keep the old system read-only, move new work into FigsFlow first, and let the jobs already in flight finish where they started. Your migration lead will tell you which way round suits your calendar.

What happens to our documents?

They stay in your SharePoint. FigsFlow points at the folder structure you already have rather than copying your files into a second store, so your retention policy, permissions and backups are unaffected by the move.

Do we have to wait for the quiet season?

No. Firms move mid-season by configuring first and going live on new work only. A quiet period makes it easier, but a dated plan built around your immovable deadlines matters more than the month you pick.

Does FigsFlow file anything with the CRA or FINTRAC for us?

No. FigsFlow records identity checks, risk ratings, decisions and the audit trail so your evidence exists before anyone asks for it. Reports to FINTRAC, filings with the CRA and the professional judgement behind them stay with your firm.

What does switching cost?

Plan pricing is set out in CAD on the pricing page. What switching support is included for your firm is scoped on the discovery call, once we know how much configuration and data movement is involved.

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.

See it run on your own practice.

Screen-shared, using your services, your client mix and your deadlines. You will see where FigsFlow fits, and where it does not.

Design previews, not a shipped build — we will tell you on the call what is live today.

9:41
SignatureEngagement letter
Ready to sign
Engagement letter 20263 signatories · you are firstSign
Audit trailIP, device and timestamp recordedOn
Also waiting
Letter of representationDue 30/09Due
HomeDocsTasksChatProfile
9:41
Tasks3 open
Upload bank statementsVAT Q3 · due todayDue
Sign engagement letterOnboarding · due 05/09Sign
Approve VAT returnQ2 · due 07/09Review
Confirm payroll changesAugust · doneClosed
HomeDocsTasksChatProfile
9:41
Client portalRidgeline Foods Ltd
Upload Sign Pay Ask
Your services
Annual accountsYear end 31/03/2026Live
VAT returnsQuarterly · next 07/10Filed
PayrollMonthly · 14 employeesCurrent
Your team
Amara · ManagerUsually replies within a day
HomeDocsTasksChatProfile
9:41
DocumentsStored in your SharePoint
Recent
Bank statement — AugUploaded by camera · 2 MBSynced
Sales ledger Q3Shared by AmaraNew
Accounts 2025Signed 14/06/2025Final
Add a document
Scan with the cameraEdges cropped automatically
HomeDocsTasksChatProfile
9:41
MessagesAmara · Manager
This job
Re: VAT Q3Amara · 2 hours agoNew
Statement attachedYou · yesterday
Next deadline
VAT Q3 filing07/10/2026 · 15 daysSoon
HomeDocsTasksChatProfile