When you move to a different PMS or channel manager, you do not simply swap the connection in Duve. The two systems identify your rooms and reservations differently, so a switch done without preparation creates duplicate rentals, duplicate reservations, and duplicate guest messages.
To avoid this, Duve runs the migration together with you. You prepare the new system and the mapping files, and on an agreed date our team moves your properties to the new connection and validates that everything syncs correctly. This article explains how the process works, what we need from you, and what to check afterward.
You are migrating from one PMS to another (for example, from Guesty to Mews) and want your existing reservations and guest journeys to carry over cleanly.
You are moving from a channel manager to a direct PMS integration, or the other way around.
Only some of your brands or properties are moving to the new system, while the rest stay on the current connection.
Before you start
Contact your Duve Customer Success Manager or Duve support. Tell us which system you are moving to, which brands or properties are moving, and the date you plan to switch. Your Duve contact will guide you through the process and stay with you until everything is fully set up and working.
Finish setting up the new system first. All rooms and reservations must already exist in the new PMS before the migration can take place.
Make sure you have Admin access to the new PMS account. This is required to set up the new connection.
Pick a quiet window. The fewer guests mid-journey, the less there is to check. Avoid a heavy arrivals day.
How the migration works
Step 1: Confirm the brands or properties that are moving
Send your Duve contact the exact names of the brands or properties that will move to the new system, as they appear in Duve. This makes sure we prepare the migration for the correct properties.
Step 2: Complete the mapping files
Your Duve contact will share two mapping files with you in a shared folder. You may be prompted to request access to the folder before you can view or edit the files.
Rooms mapping: for each room, add the existing External ID from your current system and the corresponding External ID from the new system.
Reservations mapping: for each reservation, add the existing Reservation ID from your current system and the corresponding Reservation ID from the new system.
The mapping lets Duve link your existing rooms and reservations to the new system instead of creating them again, which is what prevents duplicates and keeps your guests' pre check-in data.
Step 3: Share the access details for the new connection
Your Duve contact will add the new connection to the relevant brands in Duve. If more than one brand is moving, each brand is connected separately, so we will need the access details for each one.
For example, to retrieve the Access Token in Mews:
Log in to Mews Operations.
Go to Marketplace.
Search for Duve.
Select Duve and click Connect.
Copy the Access Token provided for the relevant property.
Share one token per brand with your Duve contact through a secure channel.
Step 4: Plan what happens to the old connection
If the brands that are moving share the same connection as brands that are not moving, Duve keeps the existing connection active for the brands that stay and moves only the relevant properties to the new connection.
Before the migration date, confirm with your Duve contact:
Whether the migrating brands will be fully disconnected from the old system.
What process will be followed on the old system's side to make sure Duve stops receiving updates for these properties once the migration takes place.
This prevents conflicting updates from the old and new systems during and after the migration.
Step 5: Turn off all your messages
Before the migration date, turn off every active message, not only the confirmation email. When the new source syncs, it can bring reservations in as new, and any message that triggers on a new reservation fires again for guests who already received it.
This includes pre-check-in reminders, upsell messages, and any other automated message, so no guest receives a second copy of a message they already got.
Tip: Export or screenshot your current list of active messages before you turn them off, so you know exactly what to turn back on later.
Step 6: Migration day
Once the new system is fully set up, the mapping files are completed, and a migration date has been agreed, Duve coordinates the migration internally with our R&D team. On the agreed date, we:
Move the relevant properties to the new connection.
Validate that rooms and reservations are syncing correctly.
Confirm with you that the migration is complete.
Note: If your account still has the legacy Confirmation Email set up and in use, Duve turns it off during the migration to avoid duplicate confirmation messages. Most accounts no longer use it, in which case no action is needed.
Step 7: Update your messages, and turn them on only after a few days
Review your messages against the new source. Field names, rate plans, and reservation statuses often differ between systems, so a message that worked with the old system may reference something that no longer arrives.
Leave the messages off for a few days after the switch. Guests who are already in-house, or who already pre checked in, would otherwise receive a second copy of messages they got before the migration. Turn them back on once those reservations have checked out. If your account uses the legacy Confirmation Email, turn it back on at the same time.
In the first days after the switch
Check these each day until you are confident everything looks right:
Last Sync on the new source is recent, within the last 10 to 15 minutes.
New reservations are arriving and land on the correct rental or room type.
Arrivals for the next few days are all present, with the right dates and guest details.
No rooms, reservations, or guests appear twice.
Guests who pre checked in before the switch still show their pre check-in, documents, and signature.
No updates are arriving from the old system for the migrated properties.
Your messages are still off, and no guest has received a duplicate message.
If something looks wrong, contact your Duve contact before changing anything. Deleting reservations or connections to fix a problem usually makes it harder to recover.
Troubleshooting
A reservation is missing after the switch: Check that it was included in the Reservations mapping file and that its room is matched to a property in Duve. Contact your Duve contact with the reservation ID.
A reservation or room appears twice: It was probably missing from a mapping file, or the old system is still sending updates. Do not delete either copy; contact your Duve contact so we can check which one holds the guest's data.
Guests received a message twice: Messages were turned back on too early, while reservations that had already been messaged were still active, or a message fired for a reservation that was not mapped. Turn the messages off again and contact your Duve contact.
Restrictions and limitations
You need Admin access to the new PMS account to set up the connection.
The migration can only take place once the new system is fully set up and both mapping files are complete.
Duve cannot merge two reservations after the fact. Accurate mapping files are what prevent duplicates.
A migration is not instant. Expect the new source to take time on its first sync, and plan for a few days of monitoring.
Tips and tricks
Fill in the mapping files early and double-check the IDs. Most issues after a migration come from a missing or incorrect ID.
Export or screenshot your current list of active messages before you turn them off in Step 5, so you know exactly what to turn back on in Step 7.
Switch early in the week, so support is available during the days you are monitoring the new connection.
FAQs
Q: Can I change the integration source myself? A: We strongly recommend running the migration with your Duve contact. The mapping files let us link your existing rooms and reservations to the new system, which you cannot do yourself, and they are what prevent duplicates.
Q: What information do I need to provide? A: The exact names of the brands or properties that are moving, the completed Rooms and Reservations mapping files, and the access details (such as a Mews Access Token) for each brand that is moving.
Q: Why is my Confirmation Email turned off during the migration? A: This applies only if your account still uses the legacy Confirmation Email. It is turned off to avoid guests receiving a second confirmation while their reservations are being moved to the new connection.
Q: Why turn off all messages and not just the confirmation email? A: Because any message that triggers on a new reservation can fire again. The new source can bring existing stays in as new reservations, so a pre-check-in reminder or an upsell message would reach guests who already received it.
Q: How long should I wait before turning messages back on? A: A few days, until the reservations that existed before the switch have checked out. Guests already in-house or already pre-checked in are the ones who would get a second copy.
Q: Only some of my brands are moving. What happens to the others? A: They stay on the existing connection, which remains active. Only the properties that are moving are transferred to the new connection.
Q: Do I need to disconnect the old system? A: For the migrating properties, the old system must stop sending updates to Duve after the migration, whether by fully disconnecting them or by another process on the old system's side. Confirm the approach with your Duve contact before the migration date.
Q: Something went wrong after the switch. What now? A: Contact your Duve contact before making any further changes. Deleting reservations or connections to clean things up often removes the data needed to fix it.
Comments
0 comments
Article is closed for comments.