Skip to main content

Migrating from One PMS to Another

This article outlines the steps required before, during, and after the migration to keep your RueBaRue integration fully functional.

Updated over 3 weeks ago

1. Pre-Migration Preparation

  • Notify RueBaRue of your migration timeline at least 15–30 days in advance.

  • Share details of the new PMS with the RueBaRue team.

  • Provide API credentials or integration access for the new PMS.

2. Migration

  • RueBaRue will temporarily turn off automated messages during migration.

  • All future bookings imported via the previous PMS will be backed up and deleted. To prevent disruptions, RueBaRue will only delete bookings from the old PMS after the final scheduled message has been sent (typically 1–30 days after the last automated message with Guestbook was sent).

  • RueBaRue will replace the existing API credentials with the new ones.

  • RueBaRue will run a script to import all future bookings from the new PMS.

3. Data Verification

RueBaRue will verify that data from your new PMS is syncing correctly:

  • Bookings and door codes are importing correctly.

  • Property IDs are not changed.

4. Macros Migration

Property macros must be updated to reflect the new PMS fields. RueBaRue will:

  • Remove current property macros and add new ones.

  • Verify macro data is importing.

  • Update master property guides and messages with new macros.

5. Final Clean-Up

  • Auto-send will be disabled for duplicate bookings.

  • Perform a final verification to ensure all data, macros, and automated processes are functioning correctly.

  • Once migration is complete, RueBaRue will reactivate all automated messages.

Did this answer your question?