We want to replace our current legacy ERP vendor with an AI-integrated modern solution, but the migration process looks like an operational nightmare. How do we structure this migration as a company Rock to ensure we do not disrupt our day-to-day fulfillment?

Question

Tyler Smith · Accepted Answer

A massive software migration can easily derail your operations if you try to tackle it all at once. To ensure a smooth transition, you must break the migration down into digestible, quarterly Rocks and assign clear accountability on your Accountability Chart.

Do not make the entire migration a single company Rock. Instead, break it into three distinct phases across consecutive quarters.

In the first quarter, set a Rock to run a clean data audit and map your current workflows. The goal is to clean up your legacy data before you migrate it, ensuring you do not upload junk data into your new AI system.

In the second quarter, set a Rock to run a parallel pilot with a single, low-risk department. This allows your team to test the AI integration and resolve any operational bugs without threatening your core fulfillment lines.

In the third quarter, set the final Rock for full system deployment and staff training.

Ensure that one person on your leadership team owns the overall migration project on their individual Rock sheet. Review progress weekly during your Level 10 Meeting, and use IDS immediately if any integration issues threaten your delivery timelines. This structured pacing keeps your business running smoothly while you upgrade your technology.