Part Six · Specialized Situations All chapters

If You Inherited or Are Stuck on Legacy Software

You didn't choose this software. Here's how to evaluate the switch you didn't sign up for

Most operators reading this guide are in exactly your position. You didn't pick your current software. It came with the marina you bought, the family business you took over, or the job you stepped into. That's a genuinely different starting point from a first-time buyer, and it deserves its own chapter, because the framework still works but the psychology and the practical constraints are different.

You didn't choose this

Someone else made this software decision, maybe years ago, and now it's yours to live with or to change. That single fact reshapes everything. You inherited not just a system but its accumulated data, its quirks, the habits your staff built around it, and a contract you never read before it was already yours.

Everything in this guide still applies to you. The five dimensions, the demo strategy, the migration reality, all of it. What changes is where you start and how you feel about starting, and pretending otherwise would be useless. So this chapter meets you where you actually are.

A new operator working through the systems they inherited, deciding what to keep and what to replace

You didn't make this decision. But you're the one who gets to make the next one.

Caution is earned

The reluctance is rational, but not a plan

If you're hesitant to switch, that instinct is earned, not a weakness. You've lived inside the consequences of a software decision you didn't make, which means you know in your bones what getting it wrong costs. First-time buyers are guessing at that risk; you've paid it. Your caution is a form of hard-won knowledge.

But there's a quiet trap in it. Staying put by default is also a decision, it's just one nobody consciously made. Chapter 3 is about how "next year" turns into never, and inherited operators are especially prone to it, because changing can feel like taking personal ownership of a risk you didn't create. It's easier to blame the software you were handed than to be the one who chose its replacement.

Here's the reframe that helps: you are not the person who made the mistake. You're the person with fresh eyes and no ego invested in the original choice. That's the single best position from which to evaluate honestly, and it's a genuine advantage a first-time buyer doesn't have.

Map what you inherited

Inventory before you shop

Before you look at a single vendor, map what you actually inherited. You can't plan an exit from a situation you haven't catalogued, and inherited situations hold surprises in both directions.

The contract. Find the renewal, termination, and data clauses your predecessor signed. You may be more locked in than you assumed, or freer, the clause discipline from Chapter 15 applied to a contract you didn't write.
The data. Expect years of accumulated mess, and decide which history genuinely matters: customer records, balances, open contracts, as in Chapter 18.
The workarounds. Catalog the spreadsheets and habits staff use to compensate for what the software can't do. Those are a precise map of the real gaps.
What actually works. Separate "everyone complains about it" from "it genuinely fails." Not everything you inherited is bad, and keeping what works saves effort and goodwill.

Try this

Write a one-page inventory before your first demo: contract status, data situation, top three workarounds, and what genuinely works. It turns a vague inherited unease into a concrete starting position, and it's the document that makes every later step easier.

Ask the people who came before

Talk to the people who came before

Someone made these decisions, and they know things that were never written down. A few conversations can save you months of guessing.

The predecessor. The previous owner or manager can tell you why this software was chosen, what the contract status really is, where the data bodies are buried, and what they'd change if they could do it again.
The seller, if you're acquiring. Get the software, contract, and data-export terms named in the purchase agreement itself. Data-export rights are far easier to secure as a condition of sale than to pry loose afterward, which is the Chapter 9 question, moved to the one moment you have maximum leverage.
The incumbent vendor. Confirm your account status, contract dates, and what leaving would actually involve, so there are no surprises mid-plan.

The goal of all of it is to disentangle someone else's decisions enough that the next one is genuinely, defensibly yours.

Through the reluctance

Move forward anyway

The reluctance is real and reasonable. Here's how to move through it without gambling.

Lean on the framework precisely because it's neutral. When you run your pains through Chapter 1, score vendors with Chapter 11, and do the net-impact math from Chapter 16, the decision rests on evidence rather than on your gut or your predecessor's ghost. A structured decision is far easier to defend, to yourself, to a board, or to the family whose business this is.

Then start with the one question that governs everything else: can you get your data out? That, from Chapter 9, is the real lock on any inherited system, and answering it tells you how free you actually are. And keep the first step small, an inventory, a sample data export, a single demo. You don't have to leap. You just have to move, and momentum does the rest.

Takeaway

You inherited the problem; you don't have to inherit the paralysis. Inventory what you were handed, talk to the people who came before, and let the framework carry the decision. Fresh eyes and no ego in the original choice are exactly what a good evaluation needs.

Or starting from paper

Next: Chapter 24

If you're moving from paper or spreadsheets

The opposite starting line: no legacy system at all, just binders, whiteboards, and spreadsheets. What changes when you're adopting software for the very first time, and why that can be an advantage.

Read Chapter 24 →

References and further reading

Sharper MMS, Map the Switch Migration Assessment, useful for a quick read on how stuck you actually are.
Association of Marina Industries (AMI), industry research and benchmark data. marinaassociation.org
Storable Marine, AMI, and Marina Dock Age, Navigating the Numbers: 2026 Marina Operator Insights & Technology Automation