Lead Management for Migration Agents: The Pipeline Your Practice Actually Needs

Migratio Editorial · Last updated 30 September 2026

TL;DR: A useful migration-agent pipeline can be simple: New enquiry → Qualified → Consultation booked → Consultation complete → Follow-up → Proposal requested → Engaged / Lost. Every opportunity should also have an owner, source and next action. The purpose is not to turn professional work into aggressive sales; it is to stop good enquiries disappearing between systems.

Migration practices often have more lead sources than they realise: Google, referrals, Facebook groups, WhatsApp, a website form, direct email, repeat clients and third-party platforms. The problem is rarely that the practice cannot create another spreadsheet. It is that no single view shows what needs attention today.

A lead pipeline should be simple enough that an agent will actually use it.

Use stages that correspond to decisions

Avoid dozens of vague status labels. A practical starting pipeline is:

New enquiry — captured but not yet assessed.
Qualified — appropriate for the practice to progress to a consultation or next step.
Consultation booked — time/service agreed.
Consultation complete — meeting happened.
Follow-up — suitable prospect who has not yet engaged.
Proposal requested — prospect has asked to proceed or receive formal scope/fees.
Engaged — formal professional engagement commenced.
Lost / not suitable — closed with a reason.

The stages can change by practice, but each should correspond to a real action or decision.

Every lead needs an owner and next action

A stage alone does not tell a team what to do. Add an owner and a next-action date. That turns a CRM from a reporting database into a working queue.

For a solo agent, the owner may always be the same person, but the next action still matters: call today, chase intake tomorrow, send proposal Friday, or no action.

Track source from the first touch

Source should be captured when the enquiry is created, not reconstructed months later. Useful categories can include Google organic, Google Ads, referral, Facebook, website direct, repeat client, partner/referrer and Migratio.

Keep the high-level source clean and store campaign or referrer detail separately. That makes later reporting far more useful.

Separate marketplace leads from the agent’s own leads

A CRM can manage both without treating them the same commercially. A marketplace opportunity may have platform-specific economics or rules. A referral or website enquiry belongs directly to the practice.

The pipeline should preserve ownership and source so the agent can use one workflow without losing control of privately generated business.

Close lost opportunities properly

“Lost” is useful only if there is a reason. Examples include price, no response, not eligible for service, timing, chose another adviser, DIY, duplicate or not within the firm’s practice area.

Over time, those reasons tell you whether the problem is marketing quality, consultation conversion, pricing, response speed or simply a poor-fit source.

The dashboard should answer today’s questions

A good lead-management home screen should show: new enquiries waiting; overdue next actions; consultations today/this week; follow-ups due; proposals requested; and recent engagements. Revenue and source analytics can sit behind that.

If the dashboard mainly displays vanity metrics, staff will go back to email.

Frequently asked questions

How many CRM stages should a migration practice have?

Start with enough stages to represent meaningful decisions, usually fewer than ten. Add detail only when it changes what someone does next.

Should every enquiry go into the CRM?

Yes if it could become work or needs a response. Otherwise source attribution and follow-up data will be incomplete.

Can one CRM track marketplace leads and the agent’s own leads?

Yes, provided ownership and source are explicit for every lead and privately generated leads are never visible to anyone outside the practice.

Compare MARA-registered migration agents