When you switch to a new Property Management System (PMS), we can migrate your historical data — bookings, groups, inventory, and rates — from your old FLYR account into your new one. Your history carries over, your Same Time Last Year (STLY) comparisons stay accurate, and your pricing models don't restart from zero.
This is a managed process. Our team handles the migration; your main job is preparing and validating a mapping file (more on that below).
What gets migrated
Data | Included |
Bookings history | ✓ |
Groups history | ✓ |
Inventory capacity history | ✓ |
Rates (BAR prices from your PMS) | ✓ |
Rate plan classifications / segment data | ✗ |
Data enrichment labels | ✗ |
Manual rate updates made inside FLYR | ✗ |
Forecasts and budgets | ✗ |
Seasonal and event settings, and notes | ✗ |
Derived pricing settings | ✗ |
Restrictions | ✗ |
Items marked with ✗ are not migrated by default and will need to be re-configured in your new FLYR account after the migration is complete. If any of these are critical for your setup, flag it to your FLYR Customer Success contact before we start.
Prerequisites
All four of these must be in place before we can begin. Missing any one of them will delay the migration.
1. Both accounts connected
Your old FLYR account must still be connected to your old PMS. Your new FLYR account must be created and connected to your new PMS.
2. Metadata synced in both accounts
Room types, rate plans, and property details must be fully synced from each PMS into their respective FLYR account. This is what allows us to match and map your data correctly.
3. A confirmed cutover date
This is the date from which all new data flows through your new PMS. The migration covers historical data up to this date — confirm it before we proceed.
4. A plan for in-house bookings
Bookings that are active on the cutover date need a clear approach. Two options:
Full migration (recommended): Your new PMS migrates all active bookings in full. We then only migrate bookings fully checked out before the cutover date.
Split migration: Bookings are checked out in the old PMS at the cutover date and re-created in the new PMS. This produces two booking records for the same stay. Tell us if this applies — it changes how we configure the migration.
The mapping file
This is the most important step, and the one that requires your input.
Your old and new PMS use different identifiers for the same room types, rate plans, and other data. We need a mapping file that connects them. Your FLYR Customer Success contact will provide the template and work with you to complete it — but you must review and formally confirm the mapping before we proceed. Errors here are the most common source of migration issues.
Two things to keep in mind:
Fields with no equivalent in the new PMS will be carried forward as-is, so nothing is lost.
Don't change any column or sheet names in the template — it will break the file during processing.
What our team does next
Once prerequisites are confirmed and the mapping file is approved:
We review your request and flag any gaps.
We schedule the migration based on data volume.
We run the migration — transferring data from your old account to your new one, applying the mapping file, and labeling migrated records for traceability.
We validate totals: booking counts and revenue figures against source data.
We notify you with a summary when it's done.
Post-migration checks
After confirmation, our Customer Success team will work with you to validate the results — spot-checking records, reviewing segment accuracy if relevant, and confirming STLY figures once recalculations have run. If anything looks off, contact us and we'll investigate.
Get started
Reach out to our FLYR Customer Success team or contact us via in-app chat. Note that historical data migrations are available as a paid add-on — our team will walk you through the details when scoping the request. The faster we get your prerequisites confirmed and mapping file signed off, the faster we can schedule.