Skip to content

Run the park

Switch on when you need it

Learn

Sign inRequest an invitation
Back to home

Moving systems is the scary part, so it has the most guardrails.

Upload what you have, map your columns to ours, read a validated preview grouped by what will happen, and roll the whole batch back in one click if it is wrong.

Request an invitationSend us a spreadsheet
Import preview, reservations.csv400 rows
✓371 will be created
✓24 will merge into an existing guest
!5 have an unreadable arrival date
Undo the whole batch for 30 days.
Step 1

Fix the five rows the preview flagged.

1

click to roll back a bad batch

0

historical totals taxed a second time

3

things you can bring: guests, reservations and sites

0

days your data is held as leverage

What actually goes wrong in a migration.

Not the upload. The five rows nobody looked at, and the totals that quietly moved.

A preview you read before anything is written.

Rows are grouped by what will happen to them: created, matched to something you already have, or stopped because something is wrong. You fix the flagged ones before committing rather than after.

Nothing is written until you commit, and committing writes the whole batch or none of it.

See the books it lands in
Day close, Thursday July 14
Collected
$4,182.40
Charges posted to folios
$612.75
In house tonight
63
✓Drawer counted and closed, $2 over
✓11 arrivals checked in
!Blocker: 1 arrival with no decision
Sets the day lock on payments, refunds and charges dated July 14.
Try it

Resolve the flagged arrival, then close the day.

Your season lands on the board.

Past reservations keep their history and future ones arrive as bookings your desk can work, with their totals intact rather than recalculated at today’s rates and taxed a second time.

Once it is in, your data stays exportable. That includes the day you decide to leave, which is the only day the promise is worth anything.

See the front desk
Reservation gridLive
Jul 15 to Jul 21
Site
Wed15
Thu16
Fri17
Sat18
Sun19
Mon20
Tue21
Site 12Full hookup, 45 ft
Site 14Full hookup, 40 ft
A2Pull through
Cabin 3Sleeps 6
Cabin 7Sleeps 4
Slip B728 ft, power
Site 18Full hookup, 32 ft
Site 20Full hookup, 40 ft
BookedIn houseHoldClosureGroup blockFlaggedLocked to the site
Step 1

Drag across a few empty nights on any row to take a booking.

A migration in an afternoon, not a quarter.

Six steps, and the point at which you can still change your mind.

UploadGuests, reservations and sites

From the export your current system already gives you.

MapYour columns to ours

Once, and remembered for the next file.

ValidateRows grouped by outcome

Created, matched, or stopped with the reason.

FixThe flagged handful

Corrected before anything is written, not after.

CommitAll of it, or none

The whole batch writes together.

UndoOne click, if it is wrong

And your export is always available, including on the way out.

Fourteen guardrails on the way in.

The move is the moment an operator is most exposed, which is why this list exists.

Upload guestsUpload past reservationsUpload sitesColumn mapping to your fileA validated preview firstRows grouped by outcomeDuplicate detectionUnmatched names flaggedNothing written before you commitThe whole batch, or none of itHistorical totals kept intactNo second taxing of historyOne click rollbackExport on demand, including on exit

14 things listed right there. Ask about any of them and we will show you it working on your own park, not on a slide.

PreviousOpening a new parkNextHow it works

Send us a spreadsheet.

We will run the import preview with you on the call.

Request an invitationBack to home