Choosing a CRM for SA small businesses and not-for-profits: a practical guide

Most South Australian small businesses and not-for-profits already have a customer system. It is just spread across a spreadsheet, a shared inbox, the accounting package, a newsletter tool and the memory of whoever has been there longest. A customer relationship management (CRM) platform puts the people and organisations you deal with, and everything you have promised them, in one place the whole team can see. Chosen well, it means fewer dropped enquiries, quotes that get followed up and reports you do not have to build by hand each month. Chosen badly, it becomes another login nobody updates. This guide explains, in plain words, how to work out what you need, shortlist and test products, connect a CRM to Xero or MYOB, your website and Microsoft 365, move your data across safely, and look after privacy and marketing rules along the way. It is general guidance, not legal advice.

Signs you have outgrown spreadsheets and inboxes

• Enquiries slip through. A website form or phone message lands in one person’s inbox and nobody else knows it exists.
• Nobody can answer “where are we up to?” without ringing around, whether the question is about a quote, a client, a donor or a volunteer.
• The same customer exists five times across the spreadsheet, the accounting system and the mailing list, each with a different address.
• Reporting is a monthly project. Pipeline, renewals, funder or board reports are rebuilt by hand from exports.
• Knowledge leaves with people. When a staff member moves on, their client history and follow-ups go with their mailbox.

If two or more of these sound familiar, a CRM is likely to pay back. If none do, a well-structured shared spreadsheet and a tidy accounting system may be enough for now, and that is a perfectly sensible answer.

Write down your processes before you look at products

Every CRM demo looks good, because it is a demo. Before you book one, write a short requirements page that a vendor or implementer cannot misread:

• Your core journeys. For example: enquiry to quote to job to invoice; prospect to member renewal; donor to receipt to thank-you; referral to case to outcome. List the steps and who does each one.
• The records you track. People, organisations, deals or opportunities, jobs, cases, memberships, donations, events. Most CRMs handle the first three out of the box; the rest may need configuration or a specialist product.
• Who uses it and how. Office staff at a desk, sales or field staff on phones, volunteers with limited access, a manager who only wants a dashboard.
• The systems it must connect to. Accounting, website forms, email and calendar, e-commerce, payments, booking or rostering tools.
• Constraints. Budget range per year, the date it needs to work by, who will own it internally, and any privacy, funder or industry obligations.

Rank the requirements as must-have, should-have and nice-to-have. The must-haves become your test script. Our guide to briefing a software or website project shows how to turn this page into a brief that implementers can price consistently.

Match the type of CRM to the way you work

There is no single best CRM. The right shortlist depends mostly on how you win and serve customers and which tools your team already lives in.

Your situation	What to prioritise	Typical shortlist
Small sales team, quotes and follow-ups	A clear pipeline, reminders, email and calendar sync, a good mobile app and quote-to-invoice integration with accounting.	Sales-focused CRMs such as Pipedrive, HubSpot or Zoho CRM
Marketing-led growth	Consent-aware website forms, email campaigns, segmentation and attribution, kept separate from staff mail.	Marketing-and-sales platforms such as HubSpot, or a CRM plus a dedicated email platform
Already deep in Microsoft 365	Single sign-on, Outlook and Teams integration, Power BI reporting and low-code process changes with Power Platform.	Microsoft Dynamics 365 or a Dataverse app, or a CRM with strong Microsoft 365 connectors
Not-for-profit with donors, members or volunteers	Donation and receipt handling, recurring giving, membership renewals, volunteer records and funder reporting.	Nonprofit editions of the larger platforms, or a specialist donor or membership CRM
Service, support or case work	Cases with status and owners, service levels, a knowledge base and strict access to sensitive notes.	Service desk or case management products, or a CRM service module

Product names are examples to start your research, not recommendations; features and plans change often. Several large vendors run nonprofit discount or donation programs, so check current eligibility before you compare prices.

A note for councils: in local government, “CRM” often means customer request management, the system that logs and routes resident requests to crews and officers. That is a different problem from sales or donor management, and it usually sits alongside the council’s property, rates and records systems. Our council request and field service architecture shows how that pattern fits together.

Test with your own data and scenarios

Once you have a shortlist of two or three, ask for a trial account rather than another presentation, and run your must-have journeys yourself:

1. Load a sample of real records, say fifty contacts and organisations with their history, cleaned of anything sensitive.
2. Have the people who will use it daily walk through your top three journeys end to end, including on a phone.
3. Try the awkward cases: a person who works for two organisations, a customer who has asked not to be emailed, a job that is cancelled after invoicing.
4. Build the one report your manager or board asks for most often, without help.
5. Export everything you loaded and check the export is complete and usable. This is your exit test.

Score each product against the must-haves rather than on how much you liked the demo. If no product meets them without heavy workarounds, read our custom software or SaaS guide before deciding to build; in most cases a configured product plus a thin integration is the better answer.

Connect it to the tools you already use

A CRM that does not talk to your other systems turns into one more place to retype data. Plan the connections at the start, and decide which system owns each piece of information.

• Accounting (Xero or MYOB). The usual split is that the CRM owns customers, deals and quotes, and the accounting system owns invoices, payments and GST. Sync in one direction per field, avoid duplicate contacts and reconcile regularly. Our CRM and Xero or MYOB integration architecture walks through the design.
• Website forms. Enquiry, quote, booking and newsletter forms should create or update CRM records directly, with the consent the person gave recorded alongside. See the website forms and marketing automation architecture.
• Email and calendar. Logging client emails and meetings against the right record is what keeps history from leaving with staff. Agree what is logged automatically and what stays private.
• Sign-in. Use your existing Microsoft 365 or Google accounts with single sign-on and multi-factor authentication, so leavers lose access the day they leave. Our identity and single sign-on architecture covers the detail.
• Reporting. Built-in dashboards cover day-to-day needs. When you want to combine CRM, finance and operations data, a reporting layer such as Power BI is usually the next step; see our guide to moving from spreadsheets to Power BI.

Larger organisations with an ERP or several business systems may need an integration layer rather than point-to-point connectors. Our Dynamics 365 and Power Platform and Salesforce and ERP integration architectures show what that looks like at the next size up.

Migrate and clean your data once, properly

Data migration is where CRM projects most often slip. Treat it as its own piece of work:

• Decide what not to bring. Old leads with no contact in years, test records and duplicates can stay behind in an archived export.
• De-duplicate before you import, matching on email address, phone and ABN, and decide which version of each record wins.
• Map fields deliberately, including picklist values such as status, source and region, so reports work from day one.
• Bring consent with the contact. If you cannot show that someone agreed to marketing email, do not import them into a marketing list.
• Run a trial import, check a sample with the people who know the customers, then do the final cut-over over a quiet period.

Privacy, marketing email and security

A CRM concentrates personal information, which makes it valuable to your team and to anyone who should not have it.

• Privacy Act. Many small businesses with annual turnover of $3 million or less are currently exempt from the Australian Privacy Principles, but not all: health service providers, businesses that trade in personal information and some contracted service providers are covered regardless, and reforms to the exemption have been proposed. Not-for-profits that hold health or sensitive information, or work under government contracts, often carry privacy obligations through their funding agreements. Either way, collect only what you need, tell people why, and limit who can see sensitive notes. Our guide to the Privacy Act and Notifiable Data Breaches explains the obligations that apply when they do.
• Where the data lives. Some CRM vendors offer Australian data hosting, often on particular plans; others store data overseas. Ask where your data, backups and support access sit, and record the answer.
• Marketing email. Under the Spam Act 2003, commercial emails and texts need consent, must identify you as the sender, and need a working unsubscribe that is honoured promptly. Set the CRM to record consent and suppress unsubscribes automatically.
• Sending on your domain. When a CRM sends email as your business, set up SPF, DKIM and DMARC for it, ideally on a subdomain, so campaigns are delivered and cannot easily be spoofed. Our email security guide shows the safe order of steps.
• Access and exit. Turn on multi-factor authentication, give each role only the access it needs, review admin accounts, and confirm you can export all of your data in a usable format. Our guide to service provider due diligence and exit planning lists the questions to ask any SaaS vendor.

Budget for the whole cost, not the licence

Per-user pricing is only part of the cost. When comparing options over three years, include:

• Licences at the headcount you expect in year three, and the plan tier that actually includes your must-haves.
• Add-ons such as marketing contacts, extra storage, advanced reporting, AI features or integration connectors.
• Setup: configuration, integrations, data migration and testing, whether done by your team or an implementer.
• Training and adoption time for every user, not just the champions.
• Ongoing ownership: someone to add fields, fix sync errors, keep integrations working when either system updates, and tidy data.

Built-in AI assistants for summarising notes or drafting emails are now common. Treat them like any other AI tool: check what data they can see, where it is processed, and what your staff are allowed to use them for. Our responsible AI adoption checklist is a short starting point.

A 90-day CRM plan

1. Weeks 1 to 2: write the requirements page, rank must-haves and name an internal owner.
2. Weeks 3 to 5: shortlist two or three products and run trials with your own data and scenarios, including the export test.
3. Week 6: choose, confirm data hosting, security settings and total three-year cost, and agree what the implementer delivers.
4. Weeks 7 to 10: configure the core journeys, connect accounting and website forms, and run a trial data import.
5. Weeks 11 to 12: train every user, cut over, and switch off the old spreadsheet so there is one source of truth.
6. Week 13: review what people actually use, fix friction, and only then add the nice-to-haves.

Common mistakes to avoid

• Buying for features you might need in five years and paying for a tier nobody uses.
• Copying every column of the old spreadsheet into custom fields, so screens become cluttered and nobody fills them in.
• Letting the old spreadsheet live on “just in case”, which guarantees two versions of the truth.
• Connecting systems in both directions without deciding which one owns each field.
• Skipping training because the product is “intuitive”.

This article reflects common practice as at late 2026. Product features, pricing and privacy law change, so confirm current details with vendors and your advisers before committing.

Talk to an Adelaide team

If you are choosing a CRM, connecting it to Xero, MYOB or your website, or moving off spreadsheets, talk it through with our team or call 0402 401 584. We will tell you plainly if the product you already pay for can do the job. You can also read about our intelligent automation, application development and data and analytics services.