Getting started
From spreadsheets to a PMS: a migration that won't lose data
Moving off spreadsheets feels risky because your whole operation lives in them. Done in the right order, it's painless.
Plenty of good properties still run on a spreadsheet and a shared inbox. It works — until it doesn't: a fat-fingered date, a booking entered twice, a rate that's three versions out of date. Moving to a real PMS is less daunting than it looks if you migrate in the right order.
Migrate in dependency order
Import the things other records depend on first, so nothing is orphaned:
- Room types and rooms — your inventory is the foundation.
- Guests — so bookings can attach to a real profile.
- Bookings — which reference both of the above.
Clean as you go
A migration is a rare chance to fix the cruft: duplicate guests, test bookings, rates nobody uses. Export a clean CSV, and you import a clean system.
Run in parallel for a week
Keep the spreadsheet alongside the PMS for a few days. Once you trust the new system with arrivals and payments, retire the spreadsheet for good.
mndra imports guests, rooms and bookings from CSV or JSON — and pulls existing reservations straight from your OTAs by iCal — so most properties are live within a day.
See how mndra puts this into practice
One calm system for reservations, channels, payments and the guest experience.