Integrate the workflow before importing the list
Agree account identifiers, duplicate handling, contact ownership, suppression and source attribution. Check whether existing customers and active opportunities are excluded or routed correctly. A provider should not create a parallel database because the permissions plan is unclear.
Use least necessary access and document workflow changes. Test imports, booking, reply routing and acceptance paths with controlled records. Product controls can behave differently across manual actions, workflows and APIs, so verify the routes actually used by the provider.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Identity and ownership | Stable account keys, contact assignment and duplicate rules | Prevent collisions with existing customer or AE work |
| Permissions | Named roles and client administrator recovery | Grant the access needed without surrendering control |
| Transitions | Research, reply and acceptance states tested | Keep automation from inventing qualified pipeline |
Work through the decision
Illustrative setup: an SDR can create account research and contact notes, but an AE accepts opportunities. A booking integration creates a provisional conversation state. A reply attaches to the existing account rather than a duplicate.
Test an active customer, a suppressed contact and a duplicate domain. Review errors before broad import. When the provider leaves, the client should retain records, field definitions and recovery instructions; removing a user should not stop an undocumented integration.
The integration bypasses the intended stage control
Do not assume interface rules apply to every automated path. Inspect current product documentation and test the actual importer or workflow. An API-created opportunity can undermine an otherwise clear qualification policy.
A concrete next step
Create a controlled CRM test pack with new, duplicate, active and suppressed accounts. Have the provider demonstrate each path and document any exception.
Sources and research notes
- Attio: Sharing and permissionsProduct documentation
- HubSpot: Pipeline rulesProduct documentation
- Attio: Back up workspace dataProduct documentation
Primary sources reviewed October 6, 2026. The operating recommendations and worked scenarios are Daavid’s analysis. Illustrative numbers are assumptions, not measured client results. Company marks identify sources and prior experience; they do not imply a customer relationship or endorsement.
Schematic