Migration agent software: what a visa practice actually needs from a CRM

Search for migration agent software and you will mostly find general-purpose CRMs with a visa-shaped label on them. They are built around a sales pipeline: leads, deals, follow-ups, close.

A migration practice does not work like that. The pipeline is real, but the actual work is assembling a complete, consistent, evidence-backed file about a person and their family, and being able to prove later how it was assembled. That is a different job, and it is where the generic tools fall down.

General information about software only. Nothing here is migration, legal or compliance advice, and it is not a guide to what OMARA requires of you. Your obligations are yours and your professional body's to define.

Four things a visa file needs that a sales CRM has no concept of

1. The file is a family, not a contact. A primary applicant, a spouse, dependants — each with their own documents, their own signatures, their own history. A CRM with one contact record per person and no way to bind them into one matter makes you keep the relationship in your head.

2. History has to be structured, not attached. Employment, education and travel history are not PDFs to file. They are dated, ordered records that need to come back out in a specific shape — qualification, institution, field of study, dates, location for a skills claim; departure and arrival dates, country and purpose for character and health declarations. If that lives in attached Word documents, every submission is a re-typing exercise, and re-typing is where errors enter.

3. Documents expire. A passport, a police check, an English test result, a skills assessment — each has a date after which it is no longer usable. A document store that cannot tell you what is about to go stale is a filing cabinet with extra steps.

4. You will be asked how it was done. Not usually, but the time it matters, it matters a great deal. Who signed what, when, from where. A signature image pasted into a PDF answers none of that.

What that means practically

One file per client, with everyone on it. Agreements, ID, structured history, jobs, invoices in one timeline, with the related people bound to the same matter rather than scattered across contact records.

Identity capture that does not mean typing. Passport MRZ scanning pulls name, date of birth, nationality and expiry straight off the document in seconds. It is a small thing that removes one of the most common sources of a wrong detail reaching a form.

Signatures with an audit trail. Per-signer IP and device recorded against the signed PDF, so the question "who signed this and when" has an answer that is not your memory. This is the same evidence model DocuSign and Adobe Sign use.

A document checklist with expiry reminders, so the stale police check surfaces before the submission, not during it.

Gated intake. Requiring ID upload before a new client gets portal access — passport-only or a 100-point combination — means the file starts complete rather than being chased into completeness.

Export in a usable shape. Structured history that comes out as CSV is the difference between preparing a submission and re-keying one.

What to ask a vendor

Ask these before the demo gets going, because the answers are usually short:

• Can one matter hold several related people, each with their own documents and signatures?
• Is employment, education and travel history structured and exportable, or just file attachments?
• Does the signature record who signed, when, and from what device and IP?
• Will it tell me a document is about to expire, before I need it?
• Can I require ID before a client gets access?
• When I leave, what do I get back, and in what format?

That last one is the question people forget, and the one that costs most later.

Where we fit, and where we do not

Trimsy does the above: one file per client with related parties bound to the matter, structured employment, education and travel history that exports as CSV, passport MRZ scanning, digital signature with per-signer IP and device recorded in the signed PDF, document checklists with expiry reminders, and configurable ID gating before portal access.

What it is not is a lodgement tool. It does not connect to departmental systems, it does not pre-fill a government form, and it does not tell you what any visa subclass requires. It handles the practice — the client file, the evidence, the agreements, the invoicing — and you do the migration work in the systems built for it.

It also runs on a flat Australian subscription from A$24.99/month with no per-client fee, which is why the phrase people search for — a cheap or free migration agent CRM — tends to land here. Worth being blunt about what free means in this category, though: a free CRM that cannot bind a family into one matter, cannot structure history and cannot evidence a signature will cost you the first time a file has to be reconstructed.

General information about software, not migration, legal or compliance advice. See how Trimsy handles migration practices or compare plans.