Overview
Salesforce integration: one version of each record across your systems
Salesforce integration makes Salesforce and your other systems share accounts, contacts, orders, invoices, cases and activity without anyone re-keying them. It matters most where Salesforce is the CRM but finance, operations, marketing or support run somewhere else: an ERP for orders and invoices, Jira for engineering escalations, Klaviyo or Marketo for email, a data warehouse for reporting.
Salesforce offers several routes in and out, and choosing the right one for each flow is most of the design. REST API handles record-level reads and writes. Bulk API 2.0 is built for large loads and extracts. Change Data Capture publishes near-real-time changes to Salesforce records, Platform Events carry custom business events, and Pub/Sub API lets other systems publish and subscribe to both without constantly polling. MuleSoft, Salesforce's integration platform, or a workflow tool such as n8n sits in the middle when a flow needs orchestration, retries and monitoring.
Great Minds is a Sydney-based systems integrator, the integrator for the gaps between platforms. We design each integration with both ends in view, because most problems come from the system on the other side: an ERP that changes customer numbers, a marketing tool with its own idea of consent. AI agents handle repetitive mapping, transformation and test work; senior consultants own the design. For the Microsoft side of a Dynamics 365 and Salesforce project, see Microsoft integration.
Capabilities
The Salesforce integrations we build
We choose the method for each flow on volume, latency and who will support it, then document it so your team can. Our broader approach to connecting platforms is on the systems integration page.
01Integration architectureA system-of-record map for every shared object, the API or middleware chosen for each flow, and API limits, error handling and security designed up front.
02Event-driven syncChange Data Capture and Platform Events delivered over Pub/Sub API, so other systems hear about new orders or updated accounts without polling Salesforce.
03Cross-platform workflowsProcesses that cross systems, such as a won opportunity creating a project in Jira or an escalated case raising an engineering issue, built in Flow, MuleSoft or n8n.
04Data and reportingSalesforce data delivered to your warehouse or BI tool through Bulk API or Data 360, so finance, sales and service report from the same numbers.Connected platforms
Platforms we connect Salesforce to
We connect Salesforce to Atlassian, Microsoft 365 and Dynamics 365, Adobe and Marketo, Klaviyo, Google Workspace, finance systems and bespoke internal applications.
For workflow automation we often use n8n, which can run in n8n's cloud or self-hosted in your own environment, alongside MuleSoft where you already run it.
How we deliver
How we deliver a Salesforce integration
Which system owns each record and field, what moves where, how often and in what volume, and what should happen when a call fails.
REST, Bulk API 2.0, Change Data Capture, Platform Events, MuleSoft or n8n, picked per flow on volume, latency, API limits and who will maintain it.
Integrations as code where possible, with retries, alerting and logs from day one, tested on real data, including duplicates, deletions and failures.
Monitoring, runbooks and documentation, then support from us or a hand-over to your team. We usually start with one connection, then extend.
Australian considerations
Data residency, privacy and APRA for Salesforce integrations
Every integration moves personal information, so the Privacy Act applies to each flow, not only to Salesforce. If middleware, logs or a SaaS connector process data offshore, that is a disclosure under APP 8 on cross-border data. And an integration that overwrites good data with bad, or copies records into an unsecured staging table, can breach the quality and security principles (APP 10 and APP 11).
Residency needs checking flow by flow. Salesforce's Hyperforce FAQ lists integrations to services not yet on Hyperforce as an exception to in-country storage. Salesforce made MuleSoft on Hyperforce generally available in Australia in August 2026, with the control plane, runtime plane and regional services hosted locally, so integration infrastructure can stay onshore. For other middleware, we check where it runs and where it writes its logs: n8n Cloud, for example, is hosted in Frankfurt, so we self-host n8n in an Australian cloud region when data must stay onshore.
For APRA-regulated entities, we document what each integration carries, where it's processed and logged, who can access it and how it fails safely. That documentation supports CPS 234 information security and CPS 230 operational risk assessments.
FAQ
Salesforce integration questions
Do we need MuleSoft to integrate Salesforce?
No. Many integrations need only Salesforce's own APIs and events, or a lighter tool such as n8n. MuleSoft earns its cost when you have many systems, APIs reused by several teams, or a need for central governance. We compare the options against your volumes and the team that will run them.
How do we avoid hitting Salesforce API limits?
Salesforce caps the number of API requests an org can make, so the design matters: Bulk API 2.0 for large volumes, events instead of polling, and changes batched rather than sent one at a time. We size each flow against your org's limits before go-live.
Should Salesforce or our ERP be the system of record?
Usually it's split by object. The ERP owns products, prices, invoices and payments; Salesforce owns leads, opportunities and customer interactions; accounts and contacts need an explicit rule for who creates and who updates. We write the rule down before building anything.
How do you integrate Salesforce with Jira?
Typically, an escalated case or a won opportunity creates a Jira issue, and status and comments flow back to Salesforce, so service and sales teams see progress without logging in to Jira. Our Atlassian integration page covers the Jira side.
Can you integrate Salesforce with Dynamics 365?
Yes. Many organisations run Dynamics 365 for finance and operations and Salesforce for CRM. We decide which system owns each record and sync from the owner, using Salesforce's APIs on one side and Dynamics 365's on the other. Our Dynamics 365 page covers the ERP side.
How do we start?
With one connection: the flow that causes the most re-keying today. We build it, run it in production and extend from there.
People
Integration architects who know both ends
Integrations are designed by senior consultants who understand Salesforce's data model and the systems it connects to, from ERPs and service desks to marketing platforms.
They stay accountable for each integration after go-live, with monitoring and documentation your team can use.
Case studies
Salesforce connected to marketing platforms
Our Salesforce integration work includes connecting Marketo and Salesforce into one marketing automation engine for Montgomery Investment Management, and moving more than a million contacts from Salesforce Marketing Cloud to Klaviyo for Meriton Suites, with consent data preserved.
Marketo and Salesforce connected for 2 fund launchesMarketo and Salesforce, connected for a global fund launchMarketo and Salesforce integrated into one marketing automation engine, so Montgomery could launch two global equity funds to the right investors at the right time.
4x faster campaign execution, 1M+ contacts migratedSalesforce Marketing Cloud to Klaviyo migration with 1M+ email marketing recipientsUnlocking personalised growth at scale through Klaviyo implementation and data migration
A 100-person firm running on Salesforce Sales CloudSalesforce CRM implementation for Hong Kong law firmDigital transformative journey of a 100-person law firm in Hong Kong powered by Salesforce Sales Cloud.Insights
Reading on Salesforce and systems integration
Migrating from Salesforce Marketing Cloud to Klaviyo: lessons from 1M+ contactsHow to move from Salesforce Marketing Cloud to Klaviyo: what the integration moves, Spam Act consent, active-profile costs, warming and cutover.
What changed in October 2026: Atlassian, Salesforce, Microsoft, Google and AdobeOctober 2026 changes for Australian IT: Atlassian Cloud price rises, Salesforce SOAP login() deadlines, Copilot licensing, Gemini data residency, OAIC.
The connected enterprise: integrating Salesforce, Atlassian, Adobe and ERPHow to connect Salesforce, Atlassian, Adobe and your ERP: system-of-record map, architecture options, API limits, APP 8 and CPS 230, and where to start.