Repurchase Strategy
You'll learn when and why replacing existing applications with commercial SaaS alternatives makes sense during cloud migration.
What is Repurchase?
The Repurchase strategy (sometimes called "Replace" or "Drop and Shop") means abandoning your current application entirely and moving to a different product—typically a cloud-native SaaS solution. Instead of migrating your custom CRM system to the cloud, you'd switch to Salesforce. Instead of hosting your own email server, you'd adopt Microsoft 365 or Google Workspace.
This is fundamentally different from the other R strategies you've learned (Rehost, Replatform, Refactor). Those move your application to the cloud. Repurchase replaces it with someone else's application.
When to Repurchase
Consider this strategy when:
- The application isn't strategic to your business—it's commodity functionality (email, HR, finance)
- Vendor solutions are mature and widely adopted in your industry
- Total cost of ownership is lower than maintaining custom code (licensing + reduced operational burden)
- Your application is outdated and would require major refactoring anyway
- Feature gaps are acceptable or outweighed by SaaS benefits (automatic updates, reliability, integrations)
The Trade-Off
Think of Repurchase like replacing your home-cooked meal service with a meal kit subscription. You lose some customization and control, but gain convenience, consistency, and time savings. You're trading flexibility for reduced operational overhead.
The key challenges: data migration to the new platform, retraining users, potential vendor lock-in, and adapting business processes to fit the SaaS product's capabilities rather than the reverse.
Key Takeaway: Repurchase replaces your application with a SaaS alternative—ideal for non-differentiating workloads where the operational simplicity and feature set of commercial products outweigh the need for custom functionality.