Switching from rezStream to Comfortly: a practical migration guide
A hands-on plan for protecting reservations, preparing your staff, and making a rezStream-to-Comfortly PMS switch feel manageable.
Switching property management systems is not an ordinary software change. Every future reservation is a promise to a real guest. Your rates have to be right, your staff has to know what to do, and the front desk still has to work the morning after the switch.
We understand why that feels risky because we are innkeepers too. We bought and ran Berry Springs Lodge, and we have been the people wondering whether tonight's arrivals, tomorrow's housekeeping list, and next month's deposits are correct.
That is why a Comfortly migration is hands-on. We review your setup with you, agree on the scope before work begins, prepare and check the new system, help your staff practice, and stay involved through the cutover and its follow-up checks. Migration help is included with Comfortly's $20 per unit, per month PMS plan, billed annually.
Will my reservations be safe?
Future reservations are the first thing we protect. Before go-live, we compare the source data with Comfortly and check the details your team will depend on:
- guest names and stay dates
- room types and room assignments
- charges, payments, deposits, and balances
- rates, minimum stays, and restrictions
- direct booking and OTA availability
An import finishing is not the same as a migration being ready. We review the results, investigate mismatches, and ask you to confirm the setup before Comfortly becomes the source of truth.
No responsible PMS company should promise that every field from an old system will map perfectly. What we can promise is that we will not hide a gap or quietly guess. We will explain what moved, what needs manual work, and what should remain in an archive.
How much work will this be for me?
You know your property; we know the migration tools and Comfortly. The work goes better when each side owns the right part.
Our team handles the technical preparation we agree on. Depending on your source data and setup, that can include extracting and importing supported records, configuring rooms and rates, reviewing mappings, connecting booking channels, and checking the new workflows.
We need you to show us how your property operates, point out unusual policies or workflows, provide the required access, and review the final setup. You should not have to become a data-migration expert. You do need to confirm that the new system reflects the way your inn actually works.
We decide the exact scope together before starting. That keeps the plan honest when a property has custom fields, unusual reports, or records that cannot move automatically.
Will my staff know what to do?
A clean import is not enough if the person opening the front desk tomorrow morning feels lost.
Before go-live, we set up staff access, walk through the jobs each person needs to do, and practice real tasks such as finding an arrival, creating a booking, taking a payment, and updating a room. We also test at least one booking from start to finish.
The training plan depends on your team. A small owner-operated inn may need something different from a property with front desk, housekeeping, and management staff. We agree on that plan with you instead of assuming one training session fits everyone.
What happens on cutover day?
A good cutover has a clear sequence and a clear stop point in the old system.
Together, we choose when rezStream stops being the place for new work. We take the agreed final export, import the remaining records, check future stays and balances, connect the required channels, and confirm that staff can complete the jobs they need that day.
We do not call the switch complete just because a command finished. The owner reviews the result before the new system becomes the source of truth.
What if something does not transfer cleanly?
Some rezStream data can be extracted and imported with our internal tools. Other settings need careful manual setup. Historical reservations, payment records, custom fields, policies, taxes, and old reports may need special handling.
We identify those limits during the migration review. If something cannot be recreated safely, we will say so and agree on another way to keep or reference it. We would rather give you a clear limitation than a confident surprise on go-live day.
Do you disappear after the switch?
No. A migration is not finished the moment Comfortly opens.
We stay involved for the follow-up period we agree on, help work through questions, and check that the new daily routines are holding up. We also recommend keeping access to rezStream for an agreed safety window. Do not cancel the old account until the review is complete and both sides agree it is safe.
Why we take this personally
We built Comfortly after operating an inn ourselves. We know a reservation is not just a row in a database. It may be an anniversary trip, a family vacation, or the room revenue that pays this week's bills.
You will work with people who understand both the software and the property behind it. We will tell you what Comfortly can do today, where the migration needs human attention, and whether we think the switch is a good fit.
The goal is not to pretend changing systems is effortless. The goal is to make the work clear, share it with you, and remove as many surprises as we can.
Talk through your property
Bring your room count, booking channels, payment setup, target timing, and the reports your team relies on. A founder will walk through the fit, the likely migration work, and the questions we would need to answer before setting a cutover date.
