What replacing a system actually costs

The quote covers the easy part

A replacement proposal arrives with licensing and implementation costed, because those are the parts a vendor can quote confidently. Everything expensive about a replacement sits outside that number.

Data migration is rarely included and is almost never trivial. Retraining a team is a real cost measured in reduced output for weeks. And the risk of running two systems during transition is borne entirely by you.

None of this argues against replacing anything. It argues for comparing the honest figure rather than the quoted one.

History is the part people forget

Years of records in an old system are not just data. They are pricing precedent, customer history, and the evidence behind decisions. In businesses that quote work based on what similar jobs cost before, losing that is a direct hit to margin.

Migration tools handle structured records reasonably well and handle context badly. Notes, attachments, and the informal record of what actually happened on a job are what get dropped, and they are frequently the most valuable part.

Ask specifically what is not coming across. The answer is more revealing than the migration plan.

People are the expensive resource

A team that is fast in an old system is slow in a new one for a while, no matter how much better the new one is. That dip is real, it lasts longer than anyone plans for, and it lands on the same people who are still expected to hit their normal numbers.

Scheduling a transition through a peak period turns that dip into a crisis. It is one of the most common avoidable mistakes in replacement projects, and it comes from planning around software timelines rather than business ones.

Will the workaround follow you?

The question that decides most replacements: what were people working around, and does the new system address it?

If a team maintains a shadow spreadsheet because the platform cannot hold a particular kind of information, and the new platform also cannot hold it, the spreadsheet reappears. You will have paid for a migration to arrive at the same operating model with a different logo.

When the answer is that the gap is unaddressed, closing the gap around the existing system is usually cheaper, faster, and lower risk than replacing it.

When replacement is right

Sometimes it is clearly correct. A platform that is genuinely end of life, a vendor whose pricing has become extractive, or a system that structurally cannot represent how the business now works.

The distinction is whether the problem is the system or the gap around it. Systems that are merely disliked are usually being blamed for a gap, and unanimity that the tool is bad is a signal to investigate rather than a mandate to shop.