Data, process, and the first week
Bringing contacts over is one project. Recreating what happens next is another. Adoption is a third: the first daily list your team will actually work. SAM can import supported files and help you design Routines. It does not copy another product's automation engine.
A reviewed move: inventory what you have, rebuild the follow-up in SAM, and check a sample before you rely on it.
What to inventory
- Contacts, households, and who owns each relationship
- Custom fields you actually use in follow-up
- Active tasks, dates, and anything promised this week
- Templates, tags, pipelines, and saved lists
- Integrations, inboxes, and permissions
How to prepare
- Export the data your current system will actually give you
- Write down the follow-up you cannot afford to miss during the move
- Separate data you can import from process you must rebuild
- Pick one daily process to run on day one in SAM
What to validate
- A sample of contacts, not only the total count
- Dates that drive Routines, after you re-enter the ones that matter
- Who can see which records
- One message template sent to a test contact
What may be manual
- Another vendor's proprietary drip or automation graph
- Historical email that the export does not include
- E-signature envelopes and files stored only in the old tool
- In-flight tasks that need a person to reassign
AI can help you describe the old follow-up and draft a SAM Routine for review. The source system still limits what you can see, and a person still checks the result. There is no promised number of days for a migration. Co-Pilot is an optional onboarding program, not a guarantee that every account receives white-glove migration.