Replatforming from an ERP is a decision that your CEO and board may instinctively resist. The investment is substantial, and the risks are real. But what they might not see as clearly is the risk of doing nothing.
As an Operator, you need to weigh your options carefully. Here’s a strategy to help you prepare for a potential replatform while maximizing the value of your current ERP.
1. Map Your Tech Stack
Start by mapping out your entire tech stack. Use a whiteboard tool like Miro to visualize all your systems and how they connect. This map will serve as a framework for discussing system changes and improvements within your business.
2. Implement an Issues Log
Create a form connected to a database where operational leaders can submit issues and track their impact. It is crucial to have documented evidence of problems, disruptions, and their effects on the business. This data will be invaluable when making a case for re-platforming.
3. Map Your Data Flows
List all your master data types—Product, Variants/SKUs, etc. For each type, identify the source and all destinations. Understanding where your data flows and where it might bottleneck is essential for evaluating your current system's efficiency.
4. Find an Integration Partner Familiar with Your ERP
This is where many ERPs begin to falter as businesses scale. Issues like server capacity, API limits, and slow loading screens often arise during spikes in order volumes. The proper integration partner can address these weak spots, but be aware that their services can be costly. Weigh these costs against the value of your ERP to determine if it's worth it.
5. Cut the ERP Out During High-Volume Periods
For brands using their ERP at scale, one effective strategy is to bypass the ERP during peak periods by connecting your eCommerce platform directly to your WMS/3PL through your integration platform. This approach can shorten the critical path for orders, reducing the risk of delays.
6. Consider a Dedicated Server
Even within a SaaS model, you can request a dedicated server for your ERP. This is especially common among larger brands that cannot afford the limitations of shared infrastructure. Although this comes at an additional cost, it can help you overcome API limits or load speed issues.
7. Avoid Vendor-Specific Solutions
If you’re seriously considering a replatform, every tech decision should be viewed through this lens. Avoid investing in solutions that are too tightly linked to your current vendor, as this could complicate or delay your migration.
Preparing for Peak Periods: A Recap
When peak season hits and your ERP starts to show its limitations, use this plan:
- Map your tech stack
- Implement an issues log
- Map your data flows
- Find an integration partner familiar with your ERP
- Cut the ERP out during high-volume periods
- Consider a dedicated server
- Avoid vendor-specific solutions
Making the Case for replatforming
If you’ve gone through this checklist and still face challenges—especially if your vendor hits you with a price increase at renewal—you should have enough evidence to convince the CEO and board to support your migration plans.