If you are a TPI advisor moving to Tern, you might be wondering what happens to the bookings that already exist in your TPISuitcase account. This article covers what to do (and what not to do) with those historical bookings during your migration, and how to handle new bookings in the meantime.
​

TPI is handling historical booking data as part of the broader Tern integration work. Do not use Tern's self-serve historical import for bookings that already live in TPISuitcase.
​

The Import agency bookings into Tern article walks agency admins through importing historical bookings from a spreadsheet. That flow is not the right path for TPI advisors migrating from Suitcase. TPI will share migration timing and next steps through your onboarding materials.
​

If you already ran a self-serve historical import for your Suitcase bookings, contact Tern support so we can help sort out any duplicates before TPI's migration work reaches your account.
​

You have two paths, depending on the booking.
​

If you need to reference or continue managing an existing Suitcase booking inside Tern before TPI's migration work is complete:

Setting Accreditation to Independent keeps the booking out of the one-way sync to TPISuitcase, so you don't push a duplicate back into Suitcase.
​

For any new booking you take from the point you join Tern:

That triggers the one-way sync to TPISuitcase. Full detail in FAQ: Tern to TPISuitcase Integration.
​

Historical Suitcase booking: A booking that lives in TPISuitcase because you or your agency created it there before joining Tern.

Independent Accreditation: A Booking Accreditation option in Tern that keeps a booking out of the one-way sync to TPISuitcase. Use this for anything you don't want pushed to Suitcase.

TPI Accreditation: The Accreditation option that triggers the sync to TPISuitcase when the booking is marked Booked.
​