“We’ll migrate later” usually means never
Projects often start with a sentence like this:
“Let’s do it this way for now. We’ll migrate later.”
The reason is usually clear. The system isn’t fully ready, but work can’t stop. Excel, a manual copy, or a temporary integration saves day one.
The problem is the second half of the sentence.
If “later” has no date, the bridge often never comes down. It becomes the process.
Temporary plan
- A two-week Excel bridge
- Then move into the main system
- We’ll remove the bridge
A “later” with no date usually means “always”.
Why the temporary path sticks
Because the bridge works.
Something that works rarely feels urgent. The team moves on to the next feature, sale, or launch. Migration drops into the “tech debt” box — visible, but owned by no one.
After a while it looks like this:
- Reports come from one place, operations from another
- New hires learn the bridge first, not the system
- Small fixes land on the bridge, not in the main product
- People say “we should migrate” — and it’s on nobody’s calendar
At that point the bridge is no longer temporary.
It is the hidden main path.
1/4 · Week 1
We agreed it was temporary
The system isn’t ready yet. Excel or a manual copy keeps work moving. Everyone knows this is temporary.
When is temporary acceptable?
I don’t ban bridges. Sometimes you need one.
But I don’t accept one without three conditions:
- An end date — a real day or sprint, not “later”
- An owner — who will close the migration, and what counts as done
- A removal rule — which data and flows must live in the main system before the bridge can shut
If those are written down, temporary can stay temporary.
If not, you’ve just built a second system — a weaker one.
Takeaway
“We’ll migrate later” is not a plan.
A plan is a date, an owner, and a done condition.
Otherwise the bridge stays.
And a year later you’re having the same conversation — only the expensive version.