Don't bring that baggage with you
October 28, 2026
You're moving to a new system for a reason. Why carry the old system's limits along with you?
My co-host Erin Wiggers on one-to-one migrations, where everything moves over just as it was, in Part 4 of 5 of our AI Readiness conversation:
"I truly just don't believe in one to one migrations… in every single situation, you're migrating for a reason. Usually that reason is a constraint of the previous system. And if you built your existing processes around constraints, that then don't exist in your new system, you don't have to bring that baggage with you."
And where that leaves the plan:
"generally, it's not a one-to-one map of the way that you didn't like before."
Before you copy a process into the new system, ask what constraint it was built around.
Where this came from
Why a Bad Process Becomes Bad Automation — AI Readiness, Part 4Watch the full conversation this clip was pulled from.
The next step

