Repurchase migration strategy, also known as 'drop and shop,' is one of the 7 Rs of migration strategies in AWS. This approach involves moving from an existing application to a different product, typically a Software-as-a-Service (SaaS) platform or cloud-native solution.
When organizations choose …Repurchase migration strategy, also known as 'drop and shop,' is one of the 7 Rs of migration strategies in AWS. This approach involves moving from an existing application to a different product, typically a Software-as-a-Service (SaaS) platform or cloud-native solution.
When organizations choose the Repurchase strategy, they abandon their current on-premises or legacy applications and adopt new cloud-based alternatives. This is particularly common when migrating from traditional licensed software to subscription-based cloud services.
Key characteristics of Repurchase include:
1. **License Transition**: Organizations move from perpetual licenses to subscription models, shifting from capital expenditure (CapEx) to operational expenditure (OpEx).
2. **Common Examples**: Moving from on-premises CRM systems to Salesforce, transitioning from self-managed email servers to Microsoft 365 or Google Workspace, or replacing legacy HR systems with Workday.
3. **Benefits**: Reduced maintenance overhead, automatic updates, improved scalability, and access to modern features. The organization no longer manages infrastructure, patching, or upgrades.
4. **Considerations**: Data migration complexity, potential feature gaps between old and new solutions, user training requirements, and integration challenges with existing systems.
5. **Cost Implications**: While initial costs may seem higher due to subscription fees, long-term total cost of ownership often decreases when factoring in eliminated maintenance, hardware, and personnel costs.
Repurchase is ideal when existing applications are outdated, when better commercial alternatives exist, or when maintaining legacy systems becomes cost-prohibitive. Organizations should evaluate SaaS solutions against their specific requirements and ensure proper data migration planning.
This strategy accelerates modernization by leveraging purpose-built cloud solutions rather than lifting and shifting problematic legacy systems. It represents a strategic decision to invest in modern platforms that align with business objectives while reducing technical debt.
Repurchase Migration Strategy - Complete Guide
What is Repurchase Migration Strategy?
Repurchase, often referred to as "drop and shop", is one of the 7 Rs of cloud migration strategies. It involves moving from an existing application to a different product, typically a Software-as-a-Service (SaaS) platform. This strategy means abandoning your current license or application and purchasing a new cloud-native solution.
Why is Repurchase Important?
1. Reduced Operational Overhead: SaaS solutions eliminate the need to manage infrastructure, patching, and maintenance.
2. Faster Time to Value: Pre-built solutions can be deployed quickly compared to re-architecting existing applications.
3. Cost Optimization: Moving to subscription-based models can reduce upfront capital expenditure and provide predictable operational costs.
4. Access to Modern Features: SaaS platforms often include the latest features, security updates, and integrations.
5. Scalability: Cloud-native SaaS solutions typically offer better scalability options.
How Repurchase Works
The repurchase process typically follows these steps:
1. Assessment: Evaluate current applications and identify candidates suitable for replacement with SaaS alternatives.
2. Vendor Selection: Research and select appropriate SaaS vendors that meet business requirements.
3. Data Migration: Extract data from legacy systems and transform it for the new platform.
4. Configuration: Set up the new SaaS solution according to organizational needs.
5. User Training: Train staff on the new platform and processes.
6. Cutover: Transition from the old system to the new SaaS solution.
Common Repurchase Examples
- Moving from on-premises CRM to Salesforce - Migrating from self-hosted email servers to Microsoft 365 or Google Workspace - Replacing legacy HR systems with Workday or SAP SuccessFactors - Switching from on-premises databases to Amazon RDS or managed database services - Moving from self-managed content management to cloud-based CMS solutions
When to Choose Repurchase
Consider repurchase when:
- The existing application requires significant effort to maintain - A mature SaaS alternative exists that meets business needs - The organization wants to reduce technical debt - There is a desire to move from CAPEX to OPEX model - The current application lacks modern features or integrations - Licensing costs for existing software are becoming prohibitive
Challenges and Considerations
- Data Migration Complexity: Moving data between different platforms can be challenging - Customization Limitations: SaaS solutions may not support all custom requirements - Vendor Lock-in: Dependency on a specific vendor's ecosystem - Training Requirements: Users need to learn new interfaces and workflows - Integration Needs: Connecting the new SaaS with existing systems may require additional work
Exam Tips: Answering Questions on Repurchase Migration Strategy
1. Identify Keywords: Look for phrases like "move to SaaS", "replace with cloud-native solution", "drop and shop", or "purchase new software".
2. Distinguish from Replatform: Repurchase involves buying a new product, while replatform involves moving the same application with some optimizations.
3. Recognize Scenarios: Questions mentioning legacy applications being replaced by well-known SaaS products typically indicate repurchase.
4. Consider Total Cost: When questions discuss reducing operational burden and moving to subscription models, repurchase is often the answer.
5. Watch for Trade-offs: Questions may test your understanding that repurchase reduces customization flexibility but increases speed of migration.
6. Remember the 7 Rs: Ensure you can differentiate repurchase from rehost, replatform, refactor, retire, retain, and relocate.
7. SaaS Indicators: When a question mentions replacing on-premises software with managed services or third-party cloud solutions, think repurchase.
8. Time Sensitivity: If a scenario emphasizes quick migration with minimal development effort, repurchase may be the optimal choice.