Skip to main content

Understanding Migrated Bookings After Moving Under a Host Agency

Written by Molly Johnson
Updated this week

Overview

When transitioning a standalone agency into a host agency within Tern, existing bookings can be migrated to align under the new host credential structure. This article explains what happens to those bookings and how to manage them after the transition.

This migration is handled by the Tern team. If your bookings have not been migrated and you think they should be, contact Tern support.

What Happens During Migration

As part of the transition:

  • Existing bookings created under your standalone agency are migrated under your host agency’s credential chain.

  • This is only done for bookings that were submitted through an accreditation that matches an accreditation of your host agency

  • This ensures that all bookings—past and future—are consolidated in one place for easier commission tracking and reconciliation.

  • Moving forward, your agents will submit bookings using the host agency credentials, keeping everything unified.


How to Reconcile Migrated Bookings

After the transition is complete:

  1. Navigate to Commission -> Statements

  2. Create a Statement - it will default to a 'Host Statement'

  3. Within the statement, you will see all relevant bookings—including migrated ones—available for reconciliation.

For a deeper walkthrough of host statements, refer to our dedicated help center article.


Identifying Migrated Bookings

Once migration is complete:

  • Any affected booking will be clearly labeled as a migrated booking when viewed in Tern.

  • This helps distinguish between bookings created before and after the transition.


Data Sync Behavior for Migrated Bookings

If you have a one-way data sync set up between Tern and your host agency:

  • Automatic sync has been intentionally suppressed for migrated bookings to prevent duplication or data conflicts.

How to Re-trigger Sync (if needed)

If you need a migrated booking to sync:

  1. Open the booking.

  2. Change the accreditation to a different option.

  3. Change it back to the correct accreditation.

  4. Save.

This action will trigger the sync to run properly.

Did this answer your question?