There's a conversation I've had more times than I can count. A business has been running on Dynamics NAV, or sometimes Sage, or something even older, for the best part of a decade. Things work. Nobody's in crisis. But there's this low-level anxiety that's been building for a while, and eventually someone picks up the phone to us and says: "We think we probably need to move. But we don't really know where to start, and honestly, we're a bit scared of what it'll cost and how long it'll take."

That's the conversation that prompted this piece. 

What struck me each time was how much uncertainty people were carrying that they didn't need to carry. They'd put off having a proper conversation with us because they assumed it would be complicated, expensive, or both. And sometimes the picture is complex but so much of the anxiety comes from not having clear information to work with. When you don't know what a migration actually involves, your brain fills in the gaps. And it usually fills them with worst-case scenarios.

So we wrote this guide to answer the questions we actually get asked, in plain language, without the sales gloss. What does a migration really involve? What does it cost? What happens to all your customisations? How long does it take? And, the big one, what's the actual risk of staying put?

That last question is the one I most want people to sit with. It's very human to frame "doing nothing" as the safe option. But if you're running a platform that Microsoft is winding down support for, staying put is a decision with real consequences. The risk doesn't disappear just because you haven't decided yet.

If there's one thing I want someone to take from reading this: you have more options, and more time to act strategically, than you probably think. But that window isn't unlimited. Now is a good moment to understand what moving would look like, on your terms, not under pressure.

- The Creative Team