Worked Costings and Selection Checklists
CRM integrations with Xero, MYOB, email and phone systems: what to sync and what it costs
How CRMs connect to Xero and MYOB, Microsoft 365 or Google Workspace, web forms and VoIP phone systems, what should sync in each direction, illustrative costs and call-recording cautions.
Integrations decide whether a CRM saves time or adds re-keying. For most Australian small businesses the important ones are accounting (Xero or MYOB) so customers, quotes and invoice status line up; email and calendar (Microsoft 365 or Google Workspace) so conversations are logged automatically; web forms and e-commerce so enquiries land in the CRM; and telephony so calls can be made from and logged in the CRM. Check whether each integration is native, a paid connector app, a middleware automation or custom API work, because the cost and reliability differ. If you record calls, check the call-recording rules for your state or territory first.
This guide is part of how to choose a CRM step by step. Plan integrations alongside data migration, and check which category of CRM already includes the integrations you need in the best-fit examples by business type. Costs are illustrative.
Four ways integrations are built
| Type | How it works | Typical cost pattern (illustrative) | Watch out for |
|---|---|---|---|
| Native integration | Built by the CRM or accounting vendor | Often included, sometimes only in higher tiers | Limited fields; one-way sync only |
| Marketplace connector app | Third-party app that links the two | Monthly fee, e.g. $15–$60 a month | Another vendor, another contract and privacy review |
| Middleware automation | Tools that trigger actions between apps | Monthly fee by number of tasks, e.g. $20–$100 a month | Breaks silently when a field changes; task limits |
| Custom API integration | A developer builds it | One-off build, e.g. $3,000–$20,000, plus maintenance | API limits in your CRM tier; documentation and ownership |
Accounting: Xero and MYOB
Decide which system is the source of truth for each piece of data:
| Data | Usual source of truth | Direction |
|---|---|---|
| Customer legal name, ABN, billing address | Accounting | Accounting → CRM, or CRM → accounting on deal won |
| Contacts and decision-makers | CRM | CRM only |
| Products and prices | Accounting or inventory | Accounting → CRM |
| Quotes | CRM | CRM → accounting as a quote or draft invoice |
| Invoices and payment status | Accounting | Accounting → CRM (read-only) |
| Credit holds | Accounting | Accounting → CRM (flag) |
Questions for the trial:
- Does a won deal create a contact and invoice in Xero or MYOB correctly, with GST coded right?
- Do edits in one system overwrite the other? Which wins?
- Are duplicates created when names differ slightly?
- Can salespeople see overdue invoices before calling a customer?
- Which edition of MYOB (or which Xero plan) does the integration support?
Both Xero and MYOB have app marketplaces listing CRM connectors; check that the connector is current and supported.
Email, calendar and documents
Two-way sync with Microsoft 365 or Google Workspace logs emails and meetings against contacts. Check:
- whether sync is per user and included in your tier;
- whether private emails can be excluded;
- whether shared inboxes (sales@, info@) are supported;
- where attachments are stored, and whether that counts against a storage limit.
Under the Privacy Act, if it applies to you, logging emails into a CRM is a collection and use of personal information; your privacy policy should cover it. See the Privacy Act guide.
Web forms, e-commerce and marketing
- Web forms should create leads with source and consent captured (an unticked box with clear wording for marketing).
- E-commerce platforms should sync orders and customers, and pass marketing consent from checkout.
- Email or SMS marketing tools must share the suppression list both ways; unsubscribes must be actioned within 5 working days under the Spam Act. See the Spam Act and Do Not Call guide.
Telephony
A CRM can connect to a cloud phone (VoIP) system to give:
- click-to-call from a contact record;
- screen pop showing the caller's record when a call comes in;
- automatic call logging with duration and outcome;
- call recording and, in some products, transcription and AI summaries;
- SMS from the CRM.
Illustrative costs: cloud phone services often charge per user per month (for example $15–$45) plus call charges, and CRM calling add-ons may add a per-seat fee. Count both in your TCO.
Telemarketing rules still apply when calls are made from the CRM: calling hours, caller identification and showing your number under the telemarketing industry standard, and Do Not Call Register washing for consumer numbers.
Call recording: check the law first
Recording phone calls is regulated by federal telecommunications interception law and by state and territory surveillance or listening-device laws, which differ. Some jurisdictions allow a party to a conversation to record it in more circumstances than others, and calls across state lines can involve more than one law. The common business practice is to tell callers at the start that the call may be recorded and why, and to offer an alternative if they object. Recordings and transcripts are personal information: store them securely, limit access, and set a retention period. Get legal advice before recording sales calls routinely.
Illustrative integration budget
A 6-seat business budgets for three years:
| Integration | Approach | One-off | Recurring (3 years) |
|---|---|---|---|
| Xero | Connector app at $25 a month | $500 set-up | $900 |
| Microsoft 365 email and calendar | Native, included in tier | $0 | $0 |
| Website forms | Native form embed | $300 web developer time | $0 |
| Cloud phone | 6 users at $30 a month, plus CRM link | $400 set-up | $6,480 |
| Middleware for two small automations | $30 a month | $200 | $1,080 |
| Total | $1,400 | $8,460 |
Three-year integration cost: $9,860. Add the one-off part to the one-off field in the TCO estimator and the recurring part to the per-seat band (here $8,460 ÷ 6 = $1,410 per seat over three years).
Mistakes to avoid
- Assuming an integration exists because a logo appears on the vendor's website. Test it.
- Two-way sync without a clear source of truth, leading to overwritten data.
- Middleware automations set up by one staff member, undocumented, breaking when they leave.
- Forgetting API limits in lower CRM tiers.
- Each integration adds another party handling your customer data; review its security and hosting.
Frequently asked questions
Do I need the CRM to integrate with my accounting software?
If salespeople need to see invoices or credit status, or if won deals become invoices, yes. Otherwise a simple contact sync may be enough.
Is middleware reliable?
It is useful for simple tasks, but monitor it, document each automation, and know who owns it.
Can I keep my existing phone system?
Often, if it offers a CRM integration or an open interface. Otherwise you may need a compatible cloud phone service.
Are call transcripts covered by privacy law?
They are personal information, and covered by the Privacy Act if your business is an APP entity. Treat them as sensitive business records either way.
Sources
- Australian Communications and Media Authority — telemarketing standard, calling line identification and SMS rules
- Office of the Australian Information Commissioner — personal information in emails and call recordings
- Australian Cyber Security Centre — securing integrations and third-party apps
- Australian Taxation Office — tax invoice and GST requirements for invoices created from the CRM