Skip to main content

How to Transition from Another PMS to Opera with Event Temple

Learn how to transition your group bookings from another PMS to Opera using Event Temple, with detailed migration steps and tips

Updated over 2 weeks ago

Transitioning from your current PMS to Opera while using Event Temple can be a smooth process with the right preparation. This guide walks you through the key steps and two migration options, depending on whether your room blocks already exist in Opera.


Before You Begin

Before starting, make sure your Opera integration has been set up using OCIM. Once your credentials have been generated and approved, you can proceed with the migration steps below.

Important Pre-Checklist

To ensure a successful transition, confirm the following:

  • Your target Opera go-live date

  • You have admin access in both Event Temple and Opera

  • All reservations and group blocks have already been created in Opera (if applicable)

Having this information ready will help determine the best migration path and prevent delays.


Configure Your Opera Group Code Format

Before connecting Opera and Event Temple, you’ll need to configure your group code format in Opera.

Event Temple supports the following formats:

  • YYMMAAAA (Year, Month, Auto-incrementing number)

  • AAAAYYMM (Auto-incrementing number, Year, Month)

Make sure this is set correctly in Opera before moving forward.


Migration Path 1: Blocks Already Exist in Opera (Recommended)

If your room blocks are already set up in Opera, this is the most efficient approach.

Step 1: Prepare Event Temple

  • Disconnect your current PMS from Event Temple

  • Ensure all room codes in Event Temple exactly match those in Opera (names and codes must be identical)

Step 2: Configure Statuses in Opera

  • Review and confirm your booking statuses in Opera

  • Ensure statuses that hold inventory (e.g., Tentative) are properly configured

  • You’ll map these statuses to Event Temple in the next step

Step 3: Connect and Map Systems

  • Connect Event Temple to Opera

  • Map booking statuses between both systems

Important:
Keep Group Sync set to Manual during migration to avoid duplicate records. Once all existing bookings are linked, you can switch this back to Automatic.

Step 4: Link Existing Bookings

For each booking in Event Temple:

  1. Delete the existing room block

  2. Click Add New Room Block

  3. Select Link Existing Group

  4. Search using:

    • Group code, or

    • Group name

  5. Select the correct group from Opera

  6. Ensure the booking status matches in both systems

  7. Confirm the following details are filled in:

    • Release date

    • Group code

    • Referral source

    • Market code

    • Rate plan

  8. If available, ensure Create on PMS is set correctly

  9. Save the booking


What Happens Next?

Once everything is connected, all new bookings created in Event Temple will automatically sync to Opera when moved to Tentative or Definite status, depending on your status mapping in settings. You can adjust this at any time to control when the sync occurs.


Migration Path 2: Blocks Do Not Yet Exist in Opera

Use this option if your room blocks have not yet been created in Opera.

Step 1: Prepare for Migration

  • Disconnect your current PMS

  • Confirm your group code format is set in Opera

  • Export your GRC (Group Room Control) report of all Tentative and Definite bookings from Event Temple, as this includes blocked rooms, dates, ADR, and other key booking details

  • Ensure room codes in Event Temple match Opera exactly

Step 2: Connect and Map Systems

  • Connect Event Temple to Opera

  • Map booking statuses between systems

Important:
Keep Group Sync set to Manual during this process to prevent duplicates. Switch to Automatic only after all bookings are synced.

Step 3: Rebuild and Sync Bookings

For each Tentative or Definite booking:

  1. Change the booking status to Lead

  2. Delete the existing room block

  3. Click Add New Room Block

  4. Manually enter:

    • Group code

    • Release date

    • Referral source

    • Market code

    • Rate plan

      • (Tip: Use a custom rate plan for flexibility during negotiations)

  5. Ensure Create on PMS is selected (this can be set under Settings → Integrations)

  6. Save the booking

  7. Change the status back to Tentative or Definite

This will trigger the sync to Opera.

Additional Tip:
Update the Tentative or Definite date to reflect the original booking timeline for accurate reporting.


What Happens Next?

Once migration is complete, all new bookings created in Event Temple will automatically sync to Opera when moved to Tentative or Definite status, depending on your status mapping in settings. You can adjust this at any time to control when the sync occurs.


Key Reminders

  • Room codes and names must match exactly between Event Temple and Opera

  • You can search for existing Opera groups by group code or group name

  • Booking statuses must match across both systems for accurate syncing

  • Keep Group Sync set to Manual during migration, then switch to Automatic once complete

  • Maintain accurate Tentative and Definite dates for reporting


If you’re unsure which migration path to follow or need assistance at any stage, reach out to our support team—we’re happy to help.

Did this answer your question?