Migrate from Lodgify
Move from Lodgify to PeakSpitz, safely.
Moving off Lodgify should feel like restoring from a backup, not a leap of faith. Your short-let management tool data is read into a PeakSpitz environment of your own, checked against your real numbers, and run in parallel — while Lodgify keeps running, untouched, the whole time. Here is exactly how, step by step.
Lodgify's standout is its direct-booking website builder — it lets an independent host stand up a branded booking site, take commission-free reservations and still sync a channel manager across the big OTAs. The limit hosts tend to hit is scope: Lodgify is centred on the website and reservations, so as the business grows you often bolt on separate tools for accounting, VAT, inventory and operations. Hosts who want that branded direct-booking experience and a real back office in one system are the ones who migrate.
The safe way to leave Lodgify
Work down the list at your own pace. Nothing here is irreversible, and your current system stays live throughout.
- 1
Before you touch anything — get a backup you own
Get a copy of your data out of Lodgify that you control — a file held on your side, not just a setting inside the system. Confirm in your contract that you have the right to export, and note any renewal, notice or lock-in dates so the timing stays on your terms.
- 2
Export your data
Pull listings, bookings, guests and rate calendars out of Lodgify in the most complete format it offers — CSV, spreadsheet, or an account/API export. Take the history too, not just open items: past records, documents and contacts are worth keeping.
- 3
Send us a sample
Before you commit, send us a representative slice — a handful of customers, a few recent orders or bookings, part of your catalogue. We map it into PeakSpitz and show you the restored result, so you see exactly how your short-let management tool data lands before you move the rest.
- 4
See what maps to what
We line Lodgify up against PeakSpitz: listings, bookings, guests and rate calendars become customers, catalogue, orders, documents and ledgers in one joined-up system. Anything without an obvious home is flagged early, not discovered late.
- 5
Bring it in — a read-only restore
Your data is read into a fresh, isolated PeakSpitz environment of your own. Nothing inside Lodgify is touched, changed or switched off — it keeps running exactly as it is.
- 6
Verify against your numbers
Before you trust it, reconcile the totals — balances, counts, tax and revenue — against what Lodgify shows today. The numbers have to match before anything goes live.
- 7
Run both in parallel
Keep Lodgify live and run PeakSpitz alongside it for as long as you like. Compare like for like, move one area across first, and build trust before you depend on it. No big-bang cutover, and no deadline from us.
- 8
Cross over and decommission — on your terms
Switch over only when PeakSpitz has earned it. Keep your Lodgify export archived as a safety net, and close the old subscription when you are ready — not a moment before.
What maps where: Lodgify → PeakSpitz
Lodgify
Rentals / Properties (with Rooms)
PeakSpitz
Bookable rental items in one catalogue
Multi-room rentals map to individual units sharing availability.
Lodgify
Website builder & booking pages
PeakSpitz
Built-in online storefront
The direct-booking site is rebuilt as the storefront, with reservation and payment in one system.
Lodgify
Reservations
PeakSpitz
Bookings / orders
Lodgify
Rates & availability calendar
PeakSpitz
Rate & availability calendar per item
Lodgify
Channel Manager
PeakSpitz
OTA links re-established over the open REST API + webhooks
Lodgify
Inbox & guest details
PeakSpitz
Guest CRM with message templates
What to watch when leaving Lodgify
- ⚠
Your Lodgify booking website does not port as a site. The branded direct-booking experience is rebuilt on the PeakSpitz storefront, and the payment connection is set up fresh so new bookings take card, cash, bank and SEPA.
- ⚠
Card details stored for existing or future direct bookings do not transfer. Guests with upcoming stays re-authorise payment, so schedule the cutover around your calendar.
- ⚠
Channel-manager connections to Airbnb, Booking.com and Vrbo are re-established via the open API and re-verified per listing. Run both systems briefly in parallel to avoid a double booking during handover.
- ⚠
Rate rules and length-of-stay restrictions are re-expressed rather than imported. Rebuild minimum-stay, seasonal and gap rules so pricing matches from the first booking.
Common questions about leaving Lodgify
Direct bookings are our whole model — do we lose the website?
You keep the direct-booking model; you rebuild the site. PeakSpitz's built-in storefront replaces the Lodgify website, so guests still book direct on your brand — and the reservation, the payment and the accounting now share one system instead of three.
Will our reservation history come across?
Past reservations import as records for reference, and completed stays archive read-only. Open and future bookings migrate as live bookings so nothing on the calendar is lost.
We are small today but growing — is PeakSpitz overkill?
PeakSpitz includes unlimited users on every plan and most businesses are live in about a week without consultants, so you are not paying per seat to grow. It adds the accounting-with-VAT and operations layer as you scale, rather than making you re-platform again later.
As much help as you want
Do it yourself, or have us map your fields, run the import and reconcile the result with you. Support is a ladder — you start where you are comfortable and step up only where an area needs it.
See the full safe-migration approach →Why people leave Lodgify
PeakSpitz runs the whole business on one AI platform — not a single corner with the rest bolted on — with Spitz AI and unlimited users included. See the difference side by side.
Compare PeakSpitz vs Lodgify →Bring your Lodgify data in safely. Cross over when you are ready.
Send us a sample of your data and we will show you the restored result — no commitment, no risk to your live system.