CRM & sales ops21 categories
Plan a migration between CRMs
Moving from one CRM to another without losing history or trust.
Plan a migration from the source CRM to the target described below. Cover: object mapping and what has no equivalent, the order objects must load in, how record ownership and IDs are preserved, what happens to activity history and attachments, and how open deals are handled mid-flight. Then: what you deliberately do not migrate and why, how to validate the result beyond row counts, the rollback plan, and the cut-over sequence hour by hour. Flag the parts that always take longer than planned. Source and target:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Automation and admin. Workflows, validation, field design and the documentation nobody wrote at the time.
Related prompts
Design this HubSpot workflowAutomating something in HubSpot without discovering the edge cases in production.Write a Salesforce validation ruleStopping bad data at entry without blocking every legitimate edge case.Design the field before anyone creates itA request for a new CRM field, which is easy to add and very hard to remove.Write the lead routing rulesDeciding who gets which lead, including the cases nobody thought about.Define lifecycle stages that mean somethingWhen MQL and SQL are used differently by marketing and sales, and handovers keep failing.Audit these automations for conflictsA CRM where several workflows have accumulated and something keeps overwriting a field.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free