sf-agent-framework
Version:
AI Agent Orchestration Framework for Salesforce Development - Two-phase architecture with 70% context reduction
99 lines (79 loc) • 2.12 kB
Markdown
# Migration Planning
## Purpose
Develop comprehensive migration plans for moving data into Salesforce, ensuring
successful data transfer with minimal business disruption.
## Instructions
1. **Migration Strategy Development**
- Define migration approach
- Determine phasing strategy
- Plan cutover approach
- Design fallback options
- Set success criteria
2. **Scope Definition**
- Identify data in scope
- Define historical data needs
- Determine archival approach
- Plan reference data
- Document exclusions
3. **Sequence Planning**
- Design load sequence
- Map dependencies
- Plan parent-child order
- Schedule batch windows
- Define checkpoints
4. **Resource Planning**
- Identify team members
- Assign responsibilities
- Plan tool requirements
- Schedule activities
- Allocate environments
5. **Risk Management**
- Identify migration risks
- Develop mitigation plans
- Create contingencies
- Plan rollback procedures
- Document escalations
6. **Communication Planning**
- Identify stakeholders
- Create communication matrix
- Plan status reporting
- Schedule checkpoints
- Define success comms
## Input Requirements
- Migration assessment results
- Business requirements
- Technical constraints
- Resource availability
- Timeline requirements
- Risk tolerance
## Output Format
- Migration Plan Document:
- Executive summary
- Migration approach
- Detailed timeline
- Resource plan
- Risk mitigation plan
- Communication plan
- Success criteria
## Planning Components
- **Scope**: What to migrate
- **Approach**: How to migrate
- **Timeline**: When to migrate
- **Resources**: Who will migrate
- **Quality**: Validation approach
- **Risk**: Mitigation strategies
## Migration Phases
- Planning and design
- Development and testing
- Trial migrations
- Dress rehearsal
- Production migration
- Post-migration support
## Best Practices
- Plan thoroughly upfront
- Include all stakeholders
- Test multiple times
- Document everything
- Communicate frequently
- Prepare for issues
- Celebrate success