The Marina Software Buyer's Guide
What Happens When You Want to Leave
Data ownership, contracts, support, and vendor stability: the exit you should evaluate before the entrance
This is the dimension almost nobody evaluates, and the one that ends up costing the most. Every software choice is secretly two choices: who you're hiring, and what happens if you have to fire them. Buyers spend all their attention on the first and discover the second only when they're trying to leave, by which point their options were already set the day they signed.
You choose the exit when you choose the entrance
You met the short version of this in Chapter 1, Question 5. This is the full one, because it deserves it. The exit is the dimension that quietly decides how much leverage you'll ever have again with the vendor you pick.
Here's the trap. While the relationship is good, none of this matters. The moment it goes bad, all of it matters at once, and every option you have is constrained by terms you agreed to when you were excited about signing, not worried about leaving.
You choose your exit the day you choose your entrance. Most operators just don't realize they're choosing.
Three questions decide how trapped you could be: can you get your data out, what does the contract say about leaving, and will the vendor even still be here. A fourth, support, runs underneath all of them, because it's really about what happens when the relationship goes wrong.
Can you get your data out?
Every vendor says you own your data. Almost none volunteer what format you'll get it in, and that format is where ownership actually lives or dies. "We'll export your data" and "we'll hand you a clean, importable file" are very different promises.
What you want is a structured export with the things that make your data usable somewhere else: customer history, transaction records, slip assignments, and contract terms, all preserved and importable. A PDF dump of report pages technically honors "you own your data" while leaving you nothing you can actually migrate.
Export is PDF only. The format can't be shown to you now. You have to "contact support to arrange an export." Any of these means your data is theirs to release on their terms, not yours to take on yours.
Before signing, ask to see a sample export file, and ask plainly: "What's included, and what's lost?" Then get the export capability written into the agreement. The receiving end of this, importing into a new system, is covered in Chapter 18.
What your contract says about leaving
The contract decides how expensive leaving is, and these are the clauses that do it. Buyers skim them because they're reading to start a relationship, not end one. Vendors count on exactly that.
| Clause | What to look for |
|---|---|
| Auto-renewal | How the term renews, and the exact window you have to give notice before it locks you in for another one. |
| Termination notice | How much notice you must give to leave, and when in the term you're allowed to. |
| Early termination fees | What it costs to leave mid-term. A high enough number is a cage with a friendly name. |
| Data ownership and export rights | Your data is explicitly yours, exportable on demand, in a usable format. In writing, not in a sales email. |
| Price escalation | Whether annual increases are capped, or open-ended once you're too embedded to move. |
The time to negotiate the exit is the offer phase, when the vendor wants your signature and you still have leverage. Once you've signed, every one of these clauses is fixed. Chapter 15 goes clause by clause on what to push for.
Will the vendor still be here?
Marina software is a small market. Vendors get acquired, fold, or pivot away from the segment you're in. The company you sign with today may not be the same company, or any company, in three years. So ask the questions that surface stability.
- How long has the founding team been in the marina market specifically?
- What's your customer retention rate, and can you name marinas like mine that have stayed?
- Are you profitable, and who owns the company?
You're not auditing them. You're watching how they answer. Reasonable vendors have honest, specific responses to these. Vendors who get cagey are telling you what you need to know without meaning to.
Support belongs in this same dimension, because support is what the relationship feels like when something has gone wrong. Ask who actually answers when you call, whether it's an in-house team that knows marinas or an outsourced queue, what the real response times are, and whether any of that is committed in writing. A vendor with weak support creates its own kind of lock-in: you stay because leaving is painful, not because staying is good.
The vendor won't discuss ownership or whether they're profitable, dodges the retention question, and support means "submit a ticket" with no human and no committed response time. In a small market, that combination is how operators end up stranded.
Score your lock-in risk
Put the four together, data portability, contract terms, vendor stability, and support, and you have a single useful number: how trapped you'd be if this relationship went bad. That's your lock-in risk, and it's worth scoring deliberately rather than discovering by accident.
Vendor lock-in risk scorer
Enter a vendor's contract terms, data export capability, support responsiveness, and stability signals. Get a lock-in risk score with the reasoning behind it. Just as useful pointed at the vendor you already have as at the ones you're considering.
That last point is worth sitting with. This scorer isn't only for choosing. If you suspect you're already locked in, it tells you how much, and where the exits are. Operators in that position should read Chapter 23, which is written specifically for marinas stuck on inherited or failing software.
Evaluate the exit before you sign the entrance. Get your data-export rights and your leaving clauses in writing, and judge vendor stability and support by how openly they answer. The vendor who's comfortable telling you exactly how to leave is usually the one worth staying with.
That's all five dimensions. Chapter 15 goes deeper on negotiating the contract clauses above, and Chapter 11 turns the whole framework into a 15-question scorecard. Part Three is where you start putting real vendors through it.
The vendor landscape: how to think about the market
With the framework complete, Part Three turns to comparing real vendors. First, a map of the market: the types of vendors out there, and which category fits an operation like yours.
Read Chapter 10 →References and further reading
- Sharper MMS, Map the Switch Migration Assessment
- 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