Integration Hub
Great Minds designs, builds and runs the integrations between Salesforce, Atlassian, Dynamics 365, Adobe, Akeneo and Shopify Plus. You get a documented integration estate with an owner, a service level and a change plan for every flow.
The problem
Salesforce holds the customer, Jira holds the work, Dynamics 365 holds the order and the invoice, Akeneo holds the product, and Shopify Plus holds the storefront. Each platform works. The trouble is between them.
Because we implement these platforms as well as connect them, we design each integration around how the system is meant to be used, not just around its API. Our guide on how to integrate Atlassian with your tech stack shows the kind of trade-offs involved.
Three ways to work with us
Each stage stands on its own. Many clients start with a Health Check, fix the riskiest flows, then hand day-to-day running to us.
01 · Assess
"What are we actually running, and where's the risk?"
02 · Build
"How quickly and predictably can we close this gap?"
03 · Run
"Who owns this when it fails, and when Salesforce changes its API?"
What you own at the end
Every engagement leaves documents your team keeps and maintains, so your integrations don't depend on one person's memory, including ours.
Every flow with its owner, direction, data classification, where it's hosted and the credentials it uses.
Which system owns each field for customers, products, orders and work, and which one wins a conflict.
What it does, how to tell it's failing, how to replay it, and who to call.
Response within 1 business hour for tier 1 flows that stop revenue, 4 business hours for tier 2, and the next business day for tier 3.
Upcoming vendor deprecations and API version changes, mapped to the flows they affect.
APP 8 data-flow map, automated-decision inventory, and CPS 230/234 notes for APRA-regulated entities.
The integration register
| Flow | Direction | System of record | Business owner | Criticality | Personal data | Status |
|---|---|---|---|---|---|---|
| Salesforce cases → Jira work items | Two-way status | Salesforce (case), Jira (work) | Head of Service | Tier 1 | Name, email | ● Healthy |
| Dynamics 365 → Shopify Plus price and stock | One-way | Dynamics 365 | eCommerce Manager | Tier 1 | None | ● Healthy |
| Akeneo → Shopify Plus product content | One-way | Akeneo | Product Manager | Tier 2 | None | ● Retrying |
| Entra ID → Jira Service Management joiners and leavers | One-way | Entra ID | IT Operations | Tier 1 | Staff identity | ● Healthy |
| Shopify Plus → Klaviyo customer events | One-way | Shopify Plus | Marketing Lead | Tier 2 | Name, email, orders; hosted in the US | ● Healthy |
Sample rows for illustration. The real register is built during your Health Check.
Hub accelerators
Each accelerator includes field mappings, transformation rules, error handling and tests. We adapt it to your data model and security requirements, and deploy it in your cloud, a hybrid model or on your own infrastructure.
Service, engineering and account teams work the same issue without re-keying it.
The right description, image and price reach every channel.
Customer data reaches modelling, segmentation and campaigns without exports.
Access changes follow HR changes the same day, with an audit trail.
Closed deals and resolved cases become reusable knowledge.
Claude, ChatGPT and Rovo connect through MCP with defined access and logging. See MCP integration.
Platforms the accelerators connect
How we choose the approach
If you already run an integration platform, we build on it. If you don't, you may not need one. We decide flow by flow, based on volume, how critical it is and who will maintain it.
| Approach | Best when | Watch out for | Who usually maintains it |
|---|---|---|---|
| Marketplace app | A common two-system flow with little customisation | Fixed behaviour, licence per user, where it hosts data | Platform admin |
| Workflow platform (e.g. n8n) | A handful of flows, moderate volume, frequent change | Hosting and access control need care | Your IT team or us |
| Direct API integration | High volume or tight latency, stable requirements | Needs engineering to change | Us, or your developers |
| iPaaS (MuleSoft, Boomi, Workato) | Many flows, an existing platform team, enterprise governance | Licence cost and specialist skills | Your integration team |
How we deliver
Systems, the data each one owns, the flows between them and the workarounds people use today.
Trigger, direction, mapping, conflict rules, error handling and owner for each flow. We start from an accelerator where one fits.
Supported, versioned APIs. Real records and edge cases. Reconciled before go-live.
Monitoring, alerts, retries, runbooks and a business owner. We run it, or train your team to.
Australian obligations
Privacy Act · APP 8
When a flow copies personal information to a platform or integration service hosted overseas, APP 8 applies. Copy only the fields a flow needs.
You get: a data-flow map showing where personal information goes and where it's stored.
From 10 December 2026
Decisions about customers often draw on several systems, so no single system owner sees the whole decision. Our guide to automated decisions and the Privacy Act explains the rule.
You get: an automated-decision inventory built from your integration map.
APRA · CPS 230 and CPS 234
Integrations supporting critical operations fall under business continuity and service provider rules, and their credentials under information security.
You get: criticality tiers, continuity notes and a credential inventory per flow.
31 January 2027
Integrations that depend on a Connect app need a plan to move to Forge or another approach.
You get: a list of affected flows and a migration plan on the change calendar.
Results
Manufacturing · Microsoft Dynamics 365
60% fewer manual processes
A decade-old, heavily customised ERP replaced with Dynamics 365 and connected to Power BI, giving operations, finance and sales live dashboards and a 30% faster monthly close.
Read the case study →Global retailer · Digital asset management
300,000+ assets migrated
Creative assets from disconnected regional systems moved to one platform and connected to eCommerce and campaign tools, making campaigns and localisation three times faster.
Read the case study →Global manufacturer · Atlassian
50+ global teams on one system
Disconnected project, request and documentation apps replaced with Jira Work Management, Jira Service Management and Confluence for the product launch process.
Read the case study →Security and hosting
In your cloud, a hybrid model or on local infrastructure. You choose, and we document data residency for each flow.
Least-privilege service accounts, stored in your secrets manager and rotated every 90 days or when staff change.
Every run, failure and retry is logged, including actions taken by AI agents through MCP.
A consultant signs off every change, and changes go through your change process where you have one.
Questions
Many consultancies specialise in one platform. We implement several, including Atlassian, Salesforce, Dynamics 365, Adobe, Akeneo and Shopify Plus, and our focus is the work between them: data flows, processes that cross systems, and the AI agents that act across them.
It's a fixed price, from $15,000 ex GST, and takes three to four weeks. The final price depends on how many platforms and flows are in scope, and we agree it before we start.
Yes. We build on the platform you have and bring the governance documents, accelerators and operations. If you have only a handful of flows, direct APIs or a workflow platform can be simpler and cheaper to run.
A Marketplace app is a fixed product you configure. An accelerator is a tested starting point we adapt to your data model, security requirements and hosting, so you get a tailored integration without building every flow from scratch.
Yes, through Integration Operations, for a fixed monthly fee. We respond to incidents in AEST business hours against an agreed service level per flow, and plan upgrades when vendors change their APIs. Monitoring and automatic retries run around the clock. Or we hand over to your team with runbooks and training.
We build on supported, versioned APIs, track vendor deprecation notices on your change calendar, and plan the upgrade before the deadline, such as Atlassian's move from Connect to Forge.
Through MCP servers that vendors provide, such as Atlassian's Rovo MCP Server, or ones we build. We set which AI clients may connect, what they can read or change, and how their use is logged. Our MCP integration service covers the detail.
Integration Health Check
A fixed-scope review of your integration estate, with a register, a risk ranking and a priced roadmap.
