Process

How to choose immigration practice management software

Do not start with a feature matrix of 200 rows. Start with three live files, one owner, and a written definition of what “live” means on day 30. Everything else is decoration.

17 August 2026 12 min read For immigration professionals
Share

Choosing practice software is an operations project that people treat like buying a laptop. Laptops you can return. A half-migrated case system is how you lose a deadline and then argue about whose folder was canonical.

This is a process you can run in a Canadian RCIC or immigration law office this quarter.

Step 1: Write the failure you are escaping

One paragraph. Examples that are specific enough to test:

  • “We cannot see whose medical expires this month.”
  • “Clients WhatsApp documents and we re-file them by hand.”
  • “Two consultants use two checklists for the same PNP.”
  • “Invoices do not know the case; government fees hit the revenue account.”

If your paragraph is “we want to be more digital,” you will buy a pretty UI and keep the same mess.

Step 2: Freeze must-haves (maximum seven)

More than seven means you have no priority. A sensible RCIC set:

  1. Configurable case stages
  2. Document versions + requests + expiries
  3. Client portal with separate auth
  4. Tasks that appear on the case and the calendar
  5. Invoices with fee vs government cost
  6. Named Canadian (or acceptable) data region
  7. Export and an audit log

Nice-to-haves (AI drafts, Dropbox import, QuickBooks) go on a second list. They do not veto the deal unless they are secretly must-haves — in which case they belong above.

Step 3: The three-file demo (non-negotiable)

Sanitize real files: an Express Entry-style skilled file, a study or work permit, and a family/sponsorship file. Every vendor sees the same three. You are not rude for refusing a generic “Acme Client.”

Demo script (45–60 minutes)

  1. Create a lead from a source. Convert. Prove no re-typing.
  2. Open the case. Show stages. Change a stage. Ask where that is logged.
  3. Generate or apply a checklist. Request two documents via portal.
  4. Upload a second passport. Show version history.
  5. Enter an expiry that conflicts with a submission target. What lights up?
  6. Assign a task to someone who is not the owner. Find it on the dashboard.
  7. Draft an invoice with a government fee line. Show the client’s pay path.
  8. Ask: data region, MFA, backup, export format, who can delete a document.
  9. Ask: what happens when IRCC changes a form — who updates the template?
  10. Leave 10 minutes for their differentiator. If they need 40, they are hiding the workflow.

Red flags

  • Cannot name a cloud region
  • Overwrites documents
  • Portal is “coming soon”
  • AI that sends mail or files to government without a review step
  • Pricing that explodes per client when you are successful
  • No way to get data out
  • Implementation quoted only as “easy” with no owner on their side
  • Stages hardcoded to another country’s process

Step 4: Scorecard (same weights for every vendor)

AreaWeightNotes
Three-file workflow30Pass/fail on your must-haves
Portal + documents20Versioning, requests, client UX
Trust (hosting, MFA, audit)15Written answers
Money10Fees, plans, sync
Team fit10Roles, seats, training
Commercial10CAD, trial, migration, contract
Differentiator5AI, playbooks, integrations

Have two staff score independently. Large gaps mean the demo was a performance.

Step 5: A 30-day trial plan

  • Days 1–3. Stages, users, service catalog. No clients yet.
  • Days 4–10. All new files go in. Portal on for those clients only.
  • Days 11–20. Invoices from the system. One integration (calendar or payments), not five.
  • Days 21–30. Retrospective: what still happens in WhatsApp? Either kill that channel or fail the trial.

Success is not “we logged in.” Success is “a consultant who was sceptical completed a document round in the portal.”

Who sits in the room

Minimum: owner (budget, hosting, contract), one consultant who hates software (they will find the friction), and whoever actually requests documents (often not the RCIC). If you buy without the sceptic, you will buy a demo.

IT or a bookkeeper joins for integrations and tax, not for choosing case stages. Do not let accounting veto the portal because they have not seen it; do let them veto a trust-ledger design that cannot separate retainers if you actually hold retainers.

Contract questions (ask in writing)

  • Where is data stored, including backups and subprocessors?
  • What is the export format and typical turnaround if we leave?
  • Who owns uploaded documents — the firm, yes?
  • Uptime commitment, if any, and how incidents are communicated
  • What is not in this plan that appeared in the demo?
  • Price of extra seats, storage, and AI on the anniversary date

Verbal “we can do that” is not a term. If it matters, it is in the order form or it is a hope.

Change management in a five-person firm

Pick a go-live date for new files only. Announce the WhatsApp rule the week before, not the day after. Celebrate the first file that went from request to package without a side folder. Do not announce “we are now a digital firm.” Announce one behaviour: documents in the portal.

If a senior consultant refuses, you have a people decision. Software will not outvote a rainmaker who keeps a private drive unless the owner is willing to make the drive unofficial.

How ImmigrateOS can help

Use the script on us. ImmigrateOS is built for this workflow: configurable cases, versioned documents, portal, tasks, invoices with government fees, AI with review, Canadian regions. Trial and plan details are on pricing. Security questions belong on security.

If another product wins the three-file test, buy that product. The process is the point.

Frequently asked questions

How many vendors should I demo?

Two or three. One is a hostage situation. Five is theatre. Use the same script and the same sample files for each.

Should consultants or the owner pick?

The owner sets constraints (hosting, budget, must-have portal). The people who open files daily must click the product. If only the owner loves it, it will not be used.

What is a reasonable trial period?

Enough to run at least one file past document collection. ImmigrateOS publishes a 14-day Professional trial; confirm current terms on the pricing page. A trial you never put a real client into is a slideshow.

When is custom-built software worth it?

Almost never for a firm this size. You will pay to reinvent audit logs and document versions. Buy a platform; configure stages and playbooks.

This article is practice-management guidance for immigration professionals. It is not legal, immigration, or regulatory advice, and ImmigrateOS is not affiliated with IRCC, CICC, or any government agency. Confirm current professional obligations with the College of Immigration and Citizenship Consultants and current program rules with IRCC.

Share

Bring this script to an ImmigrateOS demo.

We would rather fail your three-file test in a walkthrough than pass a slide deck. Book a demo or start a trial with your programs.