Salesforce Integration Acceptance Checklist
A worksheet to use before you sign off on a new Salesforce integration or a repair. Ask your Salesforce integration consultant to supply the evidence for each line, not just a yes. Free to use and share.
Workflow being accepted: ..............................................
Systems involved: ..............................................
Business consequence we are preventing: ..............................................
Date reviewed: ........................ Reviewed by: ........................
1. Business identities
- ☐ Two distinct inquiries or transactions from the same customer were tested.
- ☐ Each one appears separately in every system and report that matters.
Evidence received: ..............................................
2. Data ownership
- ☐ We have a table showing which system owns each important field and relationship.
- ☐ A test with conflicting values resolved by the agreed rule.
Evidence received: ..............................................
3. Repeat safety
- ☐ The same event sent twice produced exactly one result.
- ☐ Two copies arriving at the same time produced exactly one result.
Evidence received: ..............................................
4. Completeness
- ☐ A reconciliation compares records that should have synced with records that arrived.
- ☐ A named person reviews it, and differences are explained.
Evidence received: ..............................................
5. Access
- ☐ Record counts were run as an administrator and as the integration user.
- ☐ The counts match, or every gap is documented as intentional.
Evidence received: ..............................................
6. Capacity and end-to-end testing
- ☐ Peak API usage was estimated alongside every other integration in the org.
- ☐ Testing included the destination's real automation (flows, triggers, validation rules).
- ☐ There is a documented way to catch up after missed events or an outage.
Evidence received: ..............................................
7. Authentication and configuration changes
- ☐ We have an inventory of connected apps, integration users and their permissions (no secrets written down).
- ☐ Authentication failures trigger an alert to a named person.
- ☐ There is a reauthorization runbook.
Evidence received: ..............................................
8. Ownership and handover
- ☐ A named person owns monitoring, failures, changes and vendor contracts.
- ☐ We received a data flow diagram, exceptions runbook, test results and known limitations.
- ☐ Our team could operate and safely change the integration without the original builder.
Evidence received: ..............................................
Recovery after any fix
- ☐ The affected records arrived after the fix, including any updates that were held back.
- ☐ Sign-off is based on the business outcome, not only on the configuration change.
Evidence received: ..............................................
Need help with one unreliable workflow? Contact Logic Conduit.