# Platform Limits and Replatforming Readiness > Diagnose whether constraints come from the platform, configuration, process, or skills before building a migration case. - Type: Merchant guide - Level: Intermediate - Reading time: About 5 minutes - Audience: Written for store owners, builders, and designers refining high-performance ecommerce stores. - Last updated: 2026-11-04 - Canonical page: https://academy.getzenbasket.com/merchant-questions/platform-limits-and-replatforming-readiness/ - Part of: [Merchant Questions](https://academy.getzenbasket.com/merchant-questions/) on ZenBasket Academy --- ## What you need to know ### How do I know when I've outgrown my ecommerce platform? You may have outgrown the platform when validated needs repeatedly require unsafe workarounds, excessive manual work or unacceptable cost and risk despite optimization. ### What are signs an ecommerce platform is limiting growth? Signals include capacity or architecture limits, unreliable integrations, missing governance, slow change, poor data access, and total cost disproportionate to value. ### Should slow performance mean I need a new platform? No. Diagnose code, configuration, content, apps, infrastructure and operations first; migration can reproduce the same performance problem. ### Should high app costs mean I need a new platform? Not alone. Audit app value and overlap, then compare the optimized current stack with the full cost of alternatives. ### Should missing features mean I need to replatform? Not automatically. Test whether the need is important, can be met through process or supported extension, and justifies migration risk. ### Can operational inefficiency indicate platform limitations? Yes, but determine whether inefficiency comes from platform constraints, poor configuration, fragmented tools or undocumented process. ### When is upgrading the current platform better than migrating? Upgrade when the current platform can meet requirements with lower transition risk and acceptable lifecycle cost. ### What is ecommerce replatforming? Ecommerce replatforming is moving store capabilities, data, integrations and operations from one platform or architecture to another. ### When should an ecommerce business consider replatforming? Consider it when strategic requirements, risk, scalability or lifecycle economics cannot be met acceptably through current-platform improvement. ### When should an ecommerce business avoid replatforming? Avoid replatforming when goals are unclear, data and process are unready, resources are insufficient, or the real problem has not been diagnosed. ### How do I build a business case for replatforming? Define current problems and baseline, required future outcomes, options, lifecycle costs, benefits, risks, dependencies and measurable decision criteria. ### How should replatforming ROI be calculated? Compare risk-adjusted incremental benefits and avoided costs with migration and ongoing cost over a stated horizon, including time to value. ### What hidden costs should be considered before replatforming? Include discovery, data cleanup, integrations, redesign, SEO, testing, training, dual running, downtime risk, contract exit and post-launch stabilization. ### How do I know whether the problem is really the platform? Separate platform constraints from configuration, data, process, staffing, vendor and measurement problems using evidence and targeted tests. ### A quick store check Take one platform complaint and test platform, configuration, data, process and skill explanations before proposing migration. --- ## Frequently asked questions ### Does replatforming automatically simplify operations? No. Migrating unclear processes and dirty data can reproduce or worsen complexity. ### Should the platform decision begin with vendor demos? Begin with diagnosed problems, requirements, baseline and decision criteria. ## Related articles - **Ecommerce Capacity Planning** - **Ecommerce Operations and Cost Troubleshooting**