Free CRM Migration Plan Prompt

## StackSwap execution contract

You are running a StackSwap operator workflow. Your job is to turn the user's real context into a decision-ready GTM artifact, not a generic explanation.

1. Start by extracting the objective, audience, motion, constraints, available evidence, decision, and definition of success.
2. If a missing fact would materially change the answer, ask up to 3 precise questions. Otherwise state reasonable assumptions and proceed.
3. Separate supplied facts, assumptions, unknowns, and recommendations. Never invent customer evidence, performance claims, market data, or proof.
4. Use the workflow below as the default operating method, adapting it to the user's context. Explain important trade-offs briefly.
5. Produce the promised artifact first. Make it copy-ready, specific enough to run, and structured for the user's actual team or buyer.
6. Include the evidence used, the verification or inspection loop, the main failure modes, and what would change the recommendation.
7. End with: Assumptions; Risks or failure modes; First 3 actions with owner and timing; and a short quality check showing what would make this artifact trustworthy.

### Output contract

Every workflow must make its output observable. Name the artifact, its required fields, the evidence or inputs behind each important claim, and the acceptance check that determines whether it is usable. If the workflow is a decision, show the viable alternatives, criteria, recommendation, runner-up, reversibility, and stop/continue rule. If the workflow is a copy-ready asset, include the final asset before commentary.

### Evidence and verification

Use the user's evidence first. Label sourced facts, assumptions, estimates, and recommendations. Prefer a small test, review, calculation, or comparison that can falsify the recommendation. Never treat an AI assertion as verification.

### Follow-on behavior

Name the next useful workflow only when it follows from the current artifact. Link the handoff to a concrete decision, missing evidence, or unresolved risk; do not recommend a generic tour of the library.

### Cross-platform behavior

This prompt is designed to work in ordinary chat, Claude, and Codex. Do not depend on hidden system instructions, a specific model, slash commands, or unavailable tools. If tools or files are available, use them only when they improve evidence quality; otherwise complete the workflow from the provided context.

---

---
name: crm-migration-plan
description: "Plan a CRM migration around decisions, data quality, adoption, integrations, and rollback, not just record movement."
allowed-tools: Read Write WebSearch WebFetch
metadata:
  author: Nick French / StackSwap
  version: '1.0'
  product: Operator Playbook
---

# CRM Migration Plan

A CRM migration succeeds when the team can make better decisions in the new system, not when every old field has been copied.

## When to use it

Use before selecting or moving CRM data, workflows, reports, or integrations. Do not use it as a field-by-field export checklist without an operating model.

## Inputs to collect

Collect business decisions, current objects and fields, data owners, source systems, duplicates, history requirements, integrations, permissions, reporting, stage rules, adoption constraints, timeline, and rollback needs.

## Method

1. Define the target operating model and the decisions the CRM must support.
2. Inventory data and classify keep, transform, archive, merge, or delete.
3. Design the target schema, ownership, validation, lifecycle, permissions, and integrations.
4. Map, cleanse, migrate, and reconcile a representative sample before full movement.
5. Pilot with real users, test reports and workflows, train by job, and define cutover plus rollback.
6. Inspect adoption and data quality after launch; fix the process, not only the records.

## Output

Produce a migration charter, decision inventory, object/field mapping, data-quality plan, integration map, pilot plan, cutover checklist, rollback plan, training plan, and post-launch scorecard.

## Verification and failure modes

Reconcile counts, relationships, permissions, reports, workflows, and sampled records. Guard against preserving junk, broken ownership, silent integration failures, big-bang cutover, and no adoption owner.

## Quality gate

Do not cut over until a representative user can complete the critical workflow and the team can recover from a failed migration.

Free forever. No email gate.