Integration Complexity Assessment

This assessment rates Salesforce integration complexity for one integration at a time, in seven questions. It covers the number of systems, data volume and freshness, the direction of data flow and who owns each field, error handling, authentication and existing middleware. The result is a complexity band and the points that drive it, not an estimate of cost or time. Your answers stay in your browser.

Before you start: pick one integration and write down the systems, the objects or records that move, and who owns each system. If you are planning several integrations, run the assessment for each, because one hard integration can hide behind several easy ones.

How to use the result

You get a band (Lower, Medium or Higher complexity) and a score for each area, with the biggest drivers listed first. Higher complexity usually means more design time, more testing and a stronger case for monitoring and middleware.

• Settle data ownership first. Two-way syncs without agreed field ownership are a common source of overwritten data.
• Be honest about freshness. "Within seconds" points to event-driven patterns. Salesforce Platform Events and Change Data Capture can be consumed through the Pub/Sub API, and high-volume events are retained for 72 hours, which shapes how you recover from outages.
• Plan error handling as a feature. Decide who is alerted, how failed records are retried and how you reconcile.
• Review authentication. Shared passwords and service accounts are a risk; plan for OAuth-based access.

Use the integration error handling checklist and read middleware vs point-to-point APIs before you choose a pattern.

Sources

• Salesforce Developers: subscribe to Change Data Capture events
• Salesforce Developers: event durability and retention
• Salesforce: MuleSoft