Enterprise DNA

Instead of Migration Manager

Stop renting Migration Manager. Own your immigration practice system.

We build your version around your advisers, evidence checklists and client updates. We map your Migration Manager reports, bring the agreed records across and run the system for you through Omni by Enterprise DNA.

Migration Manager lists A$339 per licence per month on a 12-month agreement, excluding GST, plus a professional fee of A$900.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription buys

The licence term sets the starting bill

Migration Manager combines case management with portals, form filling and other services. Compare the functions your practice uses with the version you want to own. Prices below exclude GST.

paid

The shorter licence term

A 12-month agreement is A$339 per licence per month. That is A$4,068 for one licence over a year, before extras.

schedule

A longer agreement for a lower rate

The monthly licence price falls to A$259 on 24 months or A$239 on 36 months.

settings

The professional fee

The pricing page adds a professional fee of A$900 to the licence arrangement.

description

The template package

MM Templates is listed at A$1,800, or A$1,400 with a 24 or 36-month agreement, plus A$50 a month for updates.

folder

The working client file

Matter checklists, file notes and recorded dates sit alongside the applications. Those are the records this free base organises for your weekly review.

dashboard

Reports and connected services

Migration Manager offers custom reports exported to Excel. Decide which reports and connections your own version needs before agreeing the migration scope.

What your version does

Run the practice from the questions that matter

Dates

See the next deadline with its source

Bring the recorded dates and the adviser responsible into the same review.

  • check Visa expiries in the next sixty days, including dates already passed
  • check Every open response, lodgement and review date
  • check The source notice reference beside each date
  • check Quiet matters checked alongside their approaching deadlines

Evidence

Separate missing documents from unfinished review

A received document still needs someone to check it. Keep both states visible.

  • check Evidence due dates and the matter each item belongs to
  • check Received documents waiting for verification
  • check Original documents awaiting a recorded return
  • check Draft evidence requests using the actual checklist

Client files

Find the recorded gaps before the file review

Check selected Australian and New Zealand record requirements against the evidence you have entered.

  • check Missing agreement references and fee descriptions
  • check Lodged applications without a copy reference
  • check Retention review dates compared with recorded last action or closure
  • check A printable file index with communications and document references

Monday review

Put workload, updates and fees beside the caseload

Use your own records to decide which adviser needs help and which client needs a response.

  • check Open matters and unverified evidence by adviser
  • check Clients with no recent recorded update
  • check Outstanding practice fees kept separate by currency
  • check Draft client reports and read-only overviews in your business colours

Make it yours

Design your own Migration Manager replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Migration Manager. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Migration Manager replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Migration Manager data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Immigration Practice for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Immigration Practice for Claude Code

Connected to your own database

Which recorded visa dates are coming up in the next sixty days?

Visa ends

Tter cl
MM-1001
Ient ki
Maya Patel
Nd du
visa-expiry
E_on da
2026-10-10
Ys_left ad
12
Viser so
Alex Morgan
Urce_ref
demo/grant-patel.pdf

Ask it anything

Ten questions to ask across your practice

These questions combine the records in the working demo. Migration Manager also supports custom reporting. Your version lets you change the questions and the rules yourself.

chat_bubble Which visa expiries are close while the matter has been quiet?
chat_bubble Which requested evidence is overdue and who owns its matter?
chat_bubble Which received documents still need verification?
chat_bubble Which advisers have the most quiet files and evidence gaps?
chat_bubble Which clients have no recent recorded update?
chat_bubble Which original documents still need a recorded return?
chat_bubble Which lodged applications lack a copy reference?
chat_bubble Which files have archive dates shorter than the recorded retention floor?
chat_bubble Which practice fees are overdue, keeping AUD and NZD separate?
chat_bubble What transfers to another adviser when a matter changes hands?

Switching

How to switch from Migration Manager

The move is less about the software and more about your own records, so how long it takes depends on how much history you choose to bring across and how closely your fields need mapping.

  1. 1

    Export your records from Migration Manager

    Migration Manager's custom reports export to Excel. Pull the reports you rely on, such as clients, matters, evidence and key dates, and save them as CSV. Check the headings and relationships against what the new system expects before going further. Confirm with Migration Manager what your account allows to export, since this can vary.

  2. 2

    Map your fields before importing

    Your Migration Manager headings will not match the new database automatically, so the fields need mapping first. Once mapped, run a preview import before committing anything. The preview rolls back completely, so nothing is written to your records yet. Only run the real import once the preview looks right.

  3. 3

    Check what the import flags

    The import skips rows it has already seen and stops on any record that changed since a previous attempt, rather than overwriting it quietly. Go through everything it flags. This is where a wrong heading or an altered source record shows up, so treat the flagged list as something to resolve, not skip past.

  4. 4

    Run both systems side by side

    Keep Migration Manager running while you work in the new database for a short stretch. Log new conversations, evidence and dates in both places during that time. This is how a missed original, an unreturned document, or a deadline that did not come across gets caught before you drop the old system.

  5. 5

    Switch off Migration Manager

    Once every open matter, deadline and piece of evidence checks out in the new database, and you have confirmed that documents and correspondence archives moved separately, retire Migration Manager. Hold on to your export files and reconciliation notes afterward, in case a question about an older record comes up later.

construction

Where the real effort goes

The real work is rarely the technical move itself. It is deciding how your own fields, categories and rules should map across, and how much history from Migration Manager is worth bringing over versus leaving in an archive. Documents and correspondence need separate handling, and every application's progress gets verified rather than assumed. Enterprise DNA handles this mapping and reconciliation directly when you have them install and run it for you.

Not ready for a call?

Get your Migration Manager switch plan by email

We will send you the step-by-step plan for moving your business off Migration Manager, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to use it

Choose who builds and runs your version

Open source

Do it yourself

Free source, MIT licence

  1. 1 Clone the repo and run npm install
  2. 2 Run npm run demo, then open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Ask /attention and review the fictional practice
  4. 4 Map your Migration Manager Excel reports to the documented CSV format, preview the import, then apply it
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your visa categories, fields, review rules and document wording
  • check Your Migration Manager reports mapped and reconciled
  • check A web front end or a different stack when your firm needs one
  • check Your agreed connections and access requirements built into your version
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installation and migration with the practice records checked
  • check Backups, document storage and agreed access controls put in place
  • check Client updates and evidence reviews fitted to your weekly process
  • check Operated alongside your business through Omni by Enterprise DNA
Book a call

Questions

Instead of Migration Manager, answered

Can my Migration Manager history come across? expand_more

Migration Manager confirms that custom reports export to Excel. The free version imports mapped CSV copies of those reports. Headings and relationships must be checked first. Documents and correspondence archives move separately, and application progress is verified before it is recorded. We handle the agreed mapping and reconciliation in your custom version.

Does this replace the portal, VEVO and government form filling? expand_more

We scope those connections and any client-facing screens as part of your custom version. The free base organises recorded matters, evidence and dates, and produces drafts for review. Your adviser keeps responsibility for government submissions and checking visa conditions.

Will it tell me that my practice is compliant? expand_more

It flags selected gaps in the information you have recorded, with sources for the Australian and New Zealand file rules. It does not certify compliance or decide a client’s immigration position. Your adviser checks source notices, document contents and the professional duties that apply to the file.

Can the team share it and keep client records private? expand_more

Yes, with a shared database and access, backup and document-storage arrangements suitable for the practice. We put those arrangements into the managed version. The free local version is for one operator, and the practice controls who receives access to its records.

What will Enterprise DNA charge? expand_more

One setup fee, then a retainer. Sam agrees the scope around your records, working rules, connections and the level of ongoing operation you want. The source is free to use yourself, with hosting and your chosen assistant paid separately.

Bring your licence bill and your Monday review

Spend 30 minutes with Sam. Walk through what Migration Manager costs, what your advisers use and which client records need to move. Leave with a clear scope for a version your practice owns.

Book a call with Sam Get the free version

Immigration Practice for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Migration Manager?

Get your version built