--- title: "When sovereignty is not worth what it costs" url: "https://sovereos.com/blog/when-sovereignty-is-not-worth-it" description: "A company selling sovereign IT should be able to say when not to buy it. Four situations where the honest recommendation is to leave things where they are." --- # When sovereignty is not worth what it costs July 9, 2026·2 min read·SovereOS Independence has a price, and it is not primarily money. It is attention, disruption, and a period where the company is worse at something it used to be fine at. That price is worth paying often enough for this to be a business, and there are situations where it clearly is not. Writing them down is partly a matter of honesty and partly self-interest: a migration nobody needed produces an unhappy company that tells other companies about it. ## When the company is about to change shape An acquisition, a merger, a major restructuring or a move into a new market within the next year. Every one of those rewrites the requirements, and IT changes made just before them get undone. Wait. Fix documentation and access in the meantime — both survive any reorganisation — and do the structural work when the shape is known. ## When the current arrangement is genuinely portable Some companies are already fine. Their data comes out cleanly, their identity is standards-based, their key systems could be moved by another supplier in a defined time. They may still be overpaying, and that is a procurement conversation rather than a transformation project. Migrating something already portable buys very little and costs the full disruption. The way to find out is the audit, which is why it is priced separately and yours to keep. If the conclusion is that you are in good shape, that is a legitimate result and the document has still paid for itself at the next renewal. ## When there is no capacity to absorb change A company in its busiest quarter, or one that has just been through a difficult system change, or one with no internal person who can carry the project. An IT transformation needs somebody inside the company with authority and attention. Without that it stalls halfway, which is the worst possible position: two systems, no owner, and everybody blaming the change for problems that predate it. ## When the binding constraint is somewhere else The most common one. A company convinced its IT is the problem, where the actual problem is that nobody owns the customer process, or the pricing is wrong, or two departments have not spoken in a year. Better IT will not fix any of that, and a supplier who takes the project anyway is selling something they know will not deliver the outcome the customer is buying it for. ## What we would suggest instead in all four cases The cheap, non-disruptive things, which are worth doing regardless and are worth more than most migrations: Write down the estate — what exists, who supplies it, what it costs, when it renews. Get credentials into a system rather than a person, with a tested recovery path. Ask each key supplier in writing what an export contains. And write the AI policy, because that one is urgent whatever else is true. That is a few weeks of unglamorous work with no migration attached. If it turns out to be all a company needs, we would rather have said so — because the alternative is a large project that made somebody worse off, and that is a reference we would have to live with for longer than the invoice. - trade-offs - migration - cost - honest advice ## Keep reading - [Your continuity plan is one person](https://sovereos.com/blog/your-continuity-plan-is-one-person) - [Nobody in your company can price the exit from your own IT](https://sovereos.com/blog/nobody-can-price-the-exit)