How to Migrate from Dockmaster to Marine OS in 14 Days (Without Disrupting Operations)

Most marinas put off leaving Dockmaster because the migration sounds painful. Honestly, it used to be: 90-day projects, parallel-system periods, manual customer re-entry. With a modern migration tool and a focused 2-week window, a single-property marina can cut over to Marine OS in 14 calendar days without disrupting daily operations.

This is the actual day-by-day playbook we use. It assumes a 50–500 slip operation with one fuel dock and a small boatyard. Larger operations and chains follow the same outline but extend Days 8–14 across multiple weeks.

#Before Day 1: prerequisites

Two weeks before kickoff, get these in place:

1. 1Confirm Dockmaster admin access — full read access to all modules and historical data.
2. 2Identify your migration owner internally. One person, not a committee. Usually the GM or office manager.
3. 3Pull current Dockmaster license keys and support contract status. Don't cancel support until after Day 14.
4. 4Schedule the cutover window. Pick a Tuesday off-season — Mondays are too busy, weekends invite catastrophe.
5. 5Decide on parallel-run length. 3 days for confident operators, 5 days for risk-averse.

#Days 1–2: discovery and account setup

Kickoff with Marine OS implementation. Two-hour video session covering:

• Walkthrough of your current Dockmaster usage — which modules, which workflows, which quirks.
• Document Dockmaster customizations that need replication (custom fields, special rate structures, naming conventions).
• Provision your Marine OS production account with seed configuration (currency, timezone, tax jurisdiction).
• Set up users and roles — dockmaster, service manager, bookkeeper, GM.
• Identify integrations to migrate: QuickBooks, Stripe, Dockwa, restaurant POS, etc.

#Days 3–5: data export and cleanup

This is where 80% of migrations succeed or fail. Your Dockmaster data has accumulated 5–20 years of inconsistencies. Now is when you decide what to clean up and what to import as-is.

1. 1Export slip inventory from Dockmaster (slip number, length, beam, depth, electrical, monthly rate). Review for duplicates and inactive slips.
2. 2Export customer master file. Identify duplicates (Mike Smith vs Michael Smith vs Mike J. Smith). Decide which to merge.
3. 3Export vessel master file. Verify HIN format, length, ownership linkage.
4. 4Export open A/R as of cutover date. This must be exact — buyer reconciliation depends on it.
5. 5Export historical reservation data (last 3–5 years). Goes into Marine OS for reporting; not operationally critical.
6. 6Export work order history if you used Dockmaster's boatyard module.

#Days 6–7: data load and validation

Marine OS ingests the exports through the Dockmaster migration tool. Slip inventory loads first (foundational), then customers, then vessels, then reservations and history.

• Marine OS team validates record counts: did all 487 slips arrive? All 1,243 active customers? All 1,820 vessels?
• You walk a sample of 20 records per entity type. Verify edge cases — multi-owner vessels, business customers, slips with multiple seasonal arrangements.
• Spot-check open A/R. Confirm balances per customer match Dockmaster within ± $0.01.
• Tag any records that didn't migrate cleanly for manual touch-up.

#Days 8–9: configuration and training

Data is in. Now configure operations to match your business:

1. 1Build the visual marina map (drag-drop, ~2 hours for a 200-slip marina).
2. 2Configure rate plans for current season + next season.
3. 3Set up cancellation policies, deposit rules, late fees.
4. 4Configure user roles and permissions.
5. 5Wire up integrations: QuickBooks sync, Stripe, Dockwa channel, restaurant POS.
6. 6Customize email and SMS templates with your branding.

Concurrent: training sessions for your team.

• GM / owner — 60 min overview + reports walkthrough.
• Dockmaster — 90 min hands-on: slip assignments, transient check-in, channel manager.
• Office / billing — 90 min: invoicing, A/R, statements, deposits.
• Service manager (if applicable) — 60 min: work orders, scheduling, technician mobile.

#Days 10–12: parallel run

Run both systems in parallel for 3–5 days. Real transactions go into Marine OS; Dockmaster gets the same transactions re-entered as a backup. Annoying but worth it.

• Take 3–5 live customer transactions per day in Marine OS as primary.
• Re-enter the same in Dockmaster for safety net.
• End-of-day reconciliation: do A/R, deposits, and revenue match?
• Document any discrepancies. Most are user errors, not system bugs.
• Confirm integrations are flowing — QuickBooks, Stripe, Dockwa.

#Day 13: final cutover prep

Last day on Dockmaster. Final reconciliation, last data sync, customer notifications.

1. 1Final A/R reconciliation — confirm Marine OS matches Dockmaster to the penny.
2. 2Pull any last-minute Dockmaster reports you might need historically.
3. 3Send customer comms wave 2: "Tomorrow at 5pm we're fully cut over. Your slip, balance, and vessel records are all in the new system."
4. 4Brief staff: tomorrow morning is Marine OS-only.
5. 5Backup Dockmaster database one last time. Archive locally and to cloud.

#Day 14: cutover and go-live

Tuesday morning. Dockmaster is read-only. Marine OS is primary.

• 8 AM: Marine OS team on standby (Slack + video room).
• First customer interaction processed in Marine OS only.
• Real-time validation throughout the day.
• End of day: review any incidents, fix any data nits.
• Customer comms wave 3: "We're live. Here's your portal login."

#Days 15–30: stabilization

Two weeks post-go-live are when the long tail of issues surfaces. Plan for it:

1. 1Daily 15-min standup with Marine OS implementation manager for first 5 business days.
2. 2Weekly 30-min check-in for weeks 2–4.
3. 3Address customer questions through the portal (most common: "where's my insurance certificate?").
4. 4Pull first month-end reports — verify reconciliation with QuickBooks.
5. 5Document any process changes for future-hire onboarding.

#Day 60: cancel Dockmaster

Two months after cutover, cancel your Dockmaster contract. Don't do it earlier — you may need read-only access for one-off historical lookups. Don't do it later — you're paying for software you don't use.

#What goes wrong (and how to prevent it)

• Dirty customer data not cleaned up beforehand → duplicate records in production. Prevention: dedupe before Day 6 load.
• Open A/R reconciliation off by hundreds of dollars → bookkeeper headache. Prevention: lock down A/R as-of date and don't take new payments until both systems show same balance.
• Staff resistance to new UI → low adoption. Prevention: training before, not after, cutover. Hands-on, not video-only.
• Customers confused about portal access → support flood. Prevention: 3-wave customer comms, with portal access link in wave 3.
• Insurance certificate gap during cutover → can't haul boats. Prevention: pre-load insurance certs in Day 6 batch, not after go-live.