Is a new system of record the right move?
A PMS switch touches every listing, every channel connection, every message template, every owner and everyone on your team. It pays off when a different system of record fits how you run. Trouble in the handoffs is a separate question, because every tool you run today hands work to whichever PMS holds the record.
Try a quick test. Write down the last five things that went wrong in your operation. For each one, ask whether a different PMS would have prevented it, or whether it happened between two tools, or between a tool and a person. Then compare your five against these two lists.
Signs a different system of record fits better
- Your business model changed. You moved from hosting your own homes to managing for owners, or the reverse, and your system of record needs to handle owner statements, commissions and payouts differently.
- A channel, payment method or market that is central to your plan isn’t available in the system you run.
- Your owners or accountant need statements and reports shaped differently from what your current setup is built to produce.
- You’re merging companies onto one system of record. Whichever system you consolidate on, the STR Squad section below shows one command view across every company, during the move and after it.
Signs the problem lives between systems
- Guests wait for answers that live in another tool, like the door code in the lock app or the cleaner’s ETA in a text thread.
- A booking moves and the turnover finds out late.
- A guest reports a broken appliance, and it shows up again in a review two stays later.
- Reviews get answered on one channel and missed on another.
- Rate changes go live without anyone checking them against the calendar.
- Month-end means exporting from four tools into one spreadsheet.
- The same handoffs come up whichever system holds the record.
If most of your five land in the first list, the checklist below is for you. If most land in the second, the STR Squad section below covers that case.
How to switch property management software: the migration checklist
This checklist applies to any move between PMSs, whichever systems you’re leaving and joining. It protects three things: live bookings, owner money and your team’s routine.
1. Export and document everything first
Before you open the new account, pull a copy of everything the old one holds. Most of it won’t move on its own.
- Reservations. Every future booking, with guest contact details, amounts paid, balances due, deposits and fees.
- Message templates and triggers. Check-in instructions, checkout reminders, review requests, and the timing rule behind each one.
- Rates and rules. Base rates, seasonal and weekend adjustments, minimum stays, fees and taxes.
- Owner records. If you manage for owners, their contracts, commission terms, current balances and past statements.
- History you’ll want later. Occupancy and revenue reports, guest history, and any message threads you need on record. Past messages and performance reports usually stay behind in the old system.
- Every connected tool. Pricing, locks, cleaning, accounting and anything else that talks to the PMS. Each one needs reconnecting.
- Your renewal date, so the overlap period doesn’t run long.
2. Build the new system before you connect any channel
Set up properties, fees, taxes, rates, templates, users and owner records in the new PMS while the old one keeps running your live listings. Guests notice nothing during this stage. Connect a channel only when the new system is ready to take over.
3. How do you move channels without double bookings?
The risk sits in the moment the channel connection changes hands. Pick a quiet window, midweek or off-season, with no check-ins or checkouts for a day if you can find one. Follow the new PMS’s instructions for each channel, which will say whether to disconnect the old connection first or let the new one take over. Either way, a listing should never have two systems pushing availability at once, and it shouldn’t sit with no connection for longer than the switch takes.
Move one property first. After each listing connects, compare its reservations and blocked dates against the Airbnb, Vrbo and Booking.com host dashboards. Those dashboards show what guests can actually book, so treat them as the source of truth. If you also sync any calendars by iCal link, update or remove the old feeds so a stale calendar can’t block or open dates.
4. What happens to bookings already in flight?
Channel reservations usually come across with the channel connection. Direct bookings often don’t, so plan to import or re-enter them. For every stay booked before the cutover and arriving after it, confirm the dates, amount paid, balance due and security deposit in the new system.
Ask both vendors how stored payment details and scheduled charges move, because cards on file often stay with the processor that took them. For guests staying during the cutover, keep their door code and message thread steady until they check out.
5. How do you close out owner statements?
If you manage for owners, cut over at a month-end. Close the month and run final owner statements in the old system, carry opening balances into the new one, and reconcile owner and trust balances before the first new statement goes out. Tell your accountant the cutover date, archive the old statements, and send owners their new portal logins with a short note on what changed.
6. What should guests hear about the switch?
Only what changes for them. Most guests never see your PMS. Rebuild your templates and triggers, then send yourself a test of each one. For every arrival in the first two weeks, check the confirmation, the check-in instructions and the door code by hand. If anything guest-facing changes, like a payment link or a guest portal, tell the affected guests before they need it.
7. Retrain the team
Cleaners, maintenance vendors, co-hosts and office staff each need to know where their work shows up now, which app to open and who gets notified. Run a short walkthrough for each role and hand out a one-page sheet of where things live. Expect questions for the first few weeks.
8. Run old and new side by side, then cancel
Keep the old account open, disconnected from every channel, for a week. At the end of each day, check the new system against this list:
- ✓New bookings appear in the new PMS within minutes of landing on each channel.
- ✓Dates you block in the new PMS show as blocked on every channel.
- ✓Scheduled guest messages send at the right times.
- ✓Door codes reach every upcoming arrival.
- ✓Pricing updates apply as expected.
- ✓Reservations match the channel dashboards, with no duplicates and nothing missing.
When a full week runs clean, cancel the old plan before its renewal date.
Where STR Squad fits, before, during and after a switch
STR Squad is the cross-functional AI command layer for short-term rentals. It sits on top of the PMS you run, plus the pricing tools, cleaning crews, vendors and locks around it. The PMS stays your system of record. We add. We don’t replace.
Inside the Squad, 42 AI agents work on 12 specialist teams, from Guest Messaging and Housekeeping to Maintenance, Reviews, Pricing and Finance, with one command orchestrator routing every signal to the team that owns it. Turning it on is a connection, not a migration. Whatever you run, we meet your stack where it is: calendar-link sync that works with any PMS, and deeper connections built one PMS at a time, with you as a design partner. Our team connects it during onboarding.
Before a switch: take the pressure off the gaps
If most of your five landed in the second list, the Squad works on those gaps directly. Guest replies get drafted from each property’s own house rules. Turnover tasks rebuild when a booking moves. Maintenance issues get triaged and matched to a vendor, with your OK at the step that spends money. Reviews from every channel get collected and answered. With the handoffs covered, you can judge your PMS on its own merits.
During a switch: the command layer stays constant
Your team keeps the same command center, the same morning briefing and the same alerts through the move. The Squad keeps its operating notes on how each property runs, and our team connects the new PMS as part of the move.
After a switch: it keeps working on the new system
The workflows you’ve approved and the audit log of every action carry over, so your team’s habits survive the move along with your reviews.
Every operation starts in Approve-first, where each action is drafted and waits for your OK. Every action shows its reasoning and lands in an audit log, and you decide which routine work runs on Auto-pilot. For a property manager’s team, it works like a second shift that never clocks out. The same engine runs for one condo or ten thousand doors, including groups whose companies run different PMSs.
Already on OwnerRez, Hospitable or Hostaway? The OwnerRez + STR Squad, Hospitable + STR Squad and Hostaway + STR Squad pages show how the Squad works on top of each one, with nothing to rip out.
Running a management company? Connect It, Keep Everything walks through what turning on the Squad looks like, and Why Your PMS & Tech Stack Vendors Matter More explains why the layer is worth more the more of your stack you keep. Every team is described on the features page.
Frequently asked questions
Will I lose my Airbnb and Vrbo reviews if I switch property management software?
No. Reviews belong to your listings on Airbnb and Vrbo, not to your PMS. As long as you reconnect the same listings instead of creating new ones, your reviews, your rating and your Superhost or Premier Host standing stay where they are.
How do I avoid double bookings when I switch PMS?
Move one listing at a time in a quiet window, and make each channel handoff in a single sitting. Never let two systems push availability to the same listing at once, and never leave a listing with no connection for longer than the switch takes. After each listing connects, check its reservations and blocked dates against that channel’s own host dashboard.
Will switching PMS affect my Superhost status?
Not by itself. Superhost is based on your rating, response rate, cancellation rate and completed stays, all tracked by Airbnb. The one thing to watch is response rate, so keep answering guests in the Airbnb app during the cutover.
What doesn’t transfer when you switch property management software?
Usually past message threads, historical performance reports, automation rules, user logins and, often, stored payment details for direct bookings. Future channel reservations generally come across with the channel connection. Export anything you need to keep before you cancel the old account.
Can I move one property first to test the new PMS?
Yes, and it is the safer way to do it. Move one listing, check it every day for a week, then move the rest in batches.
Where does STR Squad fit if I’m considering a new PMS?
Wherever you land. List the last five things that went wrong. If a different PMS would have prevented most of them, a switch may be the right call. If most of them happened in the handoffs between tools, such as guest questions, turnovers, vendors, reviews or reporting, the Squad works those handoffs on top of whichever PMS holds the record, before, during and after a move.
What happens to STR Squad if I change PMS?
It stays. STR Squad sits on top of your PMS, so our team connects the new system during the move and the Squad keeps working. Turning it on is a connection, not a migration, and your approved workflows and audit log carry over.
See the Squad on top of your stack
Staying put, mid-switch or already moved, a demo shows the Squad working an operation shaped like yours, on the PMS you run. Thirty minutes with our team.
Request a Demo. Plans use simple monthly pricing sized to your portfolio. See plan levels.