Contact and attribute preload before support history import
Create the customer contacts and required attributes before importing historical threads so every migrated record lands with the right identity and fields attached.
Why this can grow a startup
Support history without a clean identity layer is just noise in a new inbox. Preloading contacts and attributes means imported records can map to the right user, keep the right metadata, and avoid a second repair project after the migration supposedly finished. It also helps the buyer trust the move because the new system looks organized on day one instead of partially stitched together.
Company example
Intercom's migration guide says contacts must exist before conversations or tickets are imported and that custom data attributes should be created in Intercom before history is brought over.
Source and metric
Source: Intercom Help · Browse Intercom Help tactics
Every imported contact needs at minimum a user_id or email address
Source discovered: May 26, 2026
When to use it
Use this when Support, CRM, Operations is relevant to migration, identity mapping, data hygiene and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Intercom Help and identify what is directly supported.
- Choose one channel context: Support, CRM, Operations.
- Define the test around Every imported contact needs at minimum a user_id or email address.
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.