How to use this list
Choose a representative sample including linked records, old activities, ambiguous duplicates, and restricted users. Record the expected result, actual observation, issue owner, and acceptance decision for each case.
1. Record counts by type
Reconcile the intended source population with the imported population. Explain exclusions, rejected records, and deliberately archived items.
2. Contact and company relationships
Check that important links remain attached to the right records. Matching totals can conceal incorrect associations.
3. Opportunity owners and stages
Verify ownership and stage evidence against the agreed mapping. Do not let an import silently redefine the sales process.
4. Activity history
Inspect representative notes, dates, and associated activity records. Decide explicitly what historical detail remains outside the target system.
5. Duplicates and conflicting values
Test a known ambiguous match and preserve the approved resolution rule. A blind merge can erase meaningful history.
6. Communication preferences
Check that relevant restrictions survive and are honored by the proposed workflow. Do not restart outreach merely because the record is new to the target system.
7. Permissions and roles
Use representative accounts to test required and prohibited access. An administrator-only demonstration does not validate ordinary user access.
8. Integrations and retries
Test a successful transfer, a failure, and a repeated event. Check for duplicate actions and a visible recovery owner.
9. Reports and recovery plan
Reproduce agreed totals and walk through a feasible recovery decision. Resolve source-of-truth handling before live systems diverge.
Worked example
Illustrative use: imported opportunity counts match, but activities are associated with the wrong contact records. The relationship and history tests catch an issue that a count-only acceptance would miss.
Turn the list into a decision
Select the items connected to your current operating problem. Assign an owner and an evidence source to each one, then use a recent real case to test the proposed change. Keep unresolved assumptions visible and review the result before expanding the process across the business.
Related implementation resources
Discuss the operating problem
Elixir consulting starts at $5,000 per month, with final pricing based on scope. Bring a recent example, the current workflow, and the person who owns the result to define the appropriate implementation scope.