Home›Guides›CRM setup and migration
Practical guide Australian small business

A CRM your team
can work with.

Start with the customer handover: what arrives, who takes responsibility, and what should happen next. Use this checklist before buying a new platform or moving live records.

Map the work first

Write the handover before choosing the software.

Practical planning guide · Published 12 November 2026 · Automated Australia

A CRM is useful when your team can see the next action and who owns it. Start with a recent, ordinary enquiry and follow it from your website or phone to the completed job. Record where information is copied, where a reply waits and where nobody knows which person should act.

1. Define stages with an exit condition

“New”, “qualified” and “quoted” mean little unless the team agrees what moves a record forward. A new enquiry might need a service, contact method and assigned owner. A quote should move to “sent” only after the delivery system confirms it was sent, not when somebody generated a draft.

  • Entry: where the enquiry comes from and which fields are required.
  • Owner: the person or queue responsible for the next action.
  • Exit: the evidence needed to move to the next stage.
  • Exception: what happens if information is missing, duplicated or disputed.

2. Decide which system owns each field

Your booking tool may own appointment times while your accounting system owns invoice status. Document the source of truth, direction of sync and conflict rule for each connection. Otherwise an older record can overwrite a more recent correction. Check the platform's available API, permissions and subscription requirements before including an integration in the scope.

3. Test the migration on a small sample

Map the source fields to the new fields. Include an ordinary contact, a duplicate, a record with missing information and a record with multiple related jobs. Compare notes, timestamps, ownership and contact preferences after import. A matching contact count alone does not prove that the relationships or permissions are right.

Keep an export of the source data, agree when edits will pause, and define a rollback decision. Give one person responsibility for reconciling the final import before the team starts relying on it.

Interactive example

Follow one enquiry through the handover.

Interactive walkthrough · Illustrative scenarios

From enquiry to an owned next action.

Choose a scenario and step through the decisions. This demonstration uses sample states in your browser. It does not collect contact details, create CRM records or send messages.

Step 1 of 4

Check the incoming enquiry

The sample request names a service and a preferred contact method. The workflow checks that the required information is present before attempting a handover.

Example status
Received, awaiting checks
Responsible next
Intake workflow
Evidence to check
Required fields and a unique submission reference

An example reaching the final step does not confirm a live integration, message delivery or customer outcome.

Before you switch

Make the acceptance check practical.

4. Test failures as well as the ordinary journey

Try a repeated submission, a disconnected integration and an unavailable staff member. The system should make the problem visible and leave a recoverable next action. Retrying a request should not silently create another customer or send the same message twice.

5. Agree access, training and support

List who can view, edit, export and delete information. Assign the business owner for billing and administrator access. Include a short walkthrough of the daily tasks, a written handover and the support scope. Confirm what can be exported if you later change suppliers.

Use a concrete acceptance test: “A test enquiry creates one record, reaches the assigned person, and shows a follow-up draft for approval. A repeated submission is flagged. A failed connection is visible.” This is more useful than accepting a project because the dashboard looks complete.

Bring the current platform, a redacted example enquiry and the handover that causes the most friction to a CRM assessment. If a new build is being considered, compare custom software scope and costs and the automation checklist.

  1. 1Send an enquiryAbout three minutes
  2. 2Choose a timeFree assessment
  3. 3Complete your briefAfter booking

Work out the next step.

Tell us what your business needs to do better. We can help define a practical assessment and a clear scope.

About three minutes. No account needed.
No obligation to book or buy.

Prefer email? Talk to Jesse ↗

Want to talk it through? Send this enquiry first, then choose a time for your free assessment.