If your organization is still running Tessitura v15, you’re not alone. A large share of the Tessitura community is in the same position, weighing timing, budget, and internal bandwidth before committing to a migration.
Here’s the date worth circling on your calendar: December 2027. It sounds far off, but it isn’t.
Tessitura v16 isn’t just a routine update. It’s a foundational shift in how the platform handles integrations, data permissions, and pricing logic. Tessitura recommends planning the upgrade to take four to six months, and that’s before accounting for the work that may need to happen outside of Tessitura, on your website, your integrations, and the rest of your digital ecosystem. The longer your organization waits to start, the less room there is to do this well instead of just doing it fast.
This isn’t a case of change for change’s sake. The updates in v16 reflect where Tessitura and the broader software landscape is heading: more open, more flexible, more secure. For organizations still on v15, that means the gap between your current environment and where the platform is going will only widen the longer migration is put off.
Here’s what’s actually changing, and why it matters for your team.
The API Foundation Is Being Rebuilt
Tessitura v16 completes the platform’s move from SOAP to REST APIs. If your organization relies on custom integrations, such as point-of-sale tools, CRM syncs, membership portals, or any third-party system talking to Tessitura, this is the change with the most immediate technical impact, since legacy SOAP-based integrations won’t carry forward automatically. Any custom development your team or vendor built needs to be reviewed and, in many cases, rebuilt against the new REST framework.
For most organizations, this is the piece of the migration that takes the longest to scope. It’s not always obvious how many systems are quietly talking to Tessitura behind the scenes until someone sits down and maps them out, which is why this shouldn’t be a last-minute discovery.
Contact Permissions Replaces Legacy Restriction Fields
V16 introduces a more flexible, more transparent permissions model for how patron data and communication preferences are managed. This isn’t a cosmetic change; it affects how your marketing team segments audiences, how compliance rules get enforced, and how patron consent is tracked across email, direct mail, and phone outreach.
For organizations that have built years of segmentation logic on top of the old restriction fields, this is a structural change worth planning for rather than reacting to. Getting the mapping right the first time avoids downstream cleanup in your CRM and campaign tools later.
Membership Pricing Has Been Rebuilt From The Ground Up
For organizations with tiered or benefit-based membership programs, v16’s new pricing engine offers more flexibility than v15 allowed, but it also means existing membership configurations need to be mapped and validated before go-live, not after. Organizations with more complex membership structures, such as multiple tiers, add-on benefits, and donor-linked pricing, will want to give this piece extra attention, since pricing errors that surface after launch are far harder to unwind than ones caught during testing.
Don’t Let The Upgrade Timeline Dictate Your Digital Strategy
It’s worth pausing on something easy to lose sight of once a deadline is on the calendar: Tessitura is upgrading the platform. That gives your organization an opportunity to upgrade the experience. The goal shouldn’t simply be making everything compatible with v16, it’s a natural moment to ask whether the digital experience you’re carrying forward is still the one you want to be delivering.
There are many organizations that have already moved to v16 and have missed this opportunity. They treated it purely as a technical migration and left the bigger questions for another day, which usually means they don’t get asked at all.
Some questions for your team to consider before getting started:
- Are your customer journeys still working the way you want them to?
- Are there opportunities to improve performance, accessibility, AEO/SEO, or conversion while you’re already doing the work?
- Where could new v16 capabilities replace something your team built themselves to work around v15’s limitations?
The Sooner You Start, The Smoother The Migration
Bring your digital team into the conversation early. Your Tessitura team can guide you through the platform upgrade, but they can’t necessarily account for everything happening around your broader digital ecosystem. If your website relies on Tessitura APIs, shared sessions, TNEW, custom integrations, or other connections, iMedia can help you plan early. That way your strategy is in place before the scope is locked in.
A V16 migration goes best when it’s planned on your timeline, not squeezed in under pressure. Starting the assessment now gives your team room to review integrations, map permissions, and validate pricing rules at a comfortable pace. It also gets you access to V16’s ongoing security updates and platform improvements sooner rather than later.
There’s also a practical scheduling advantage to starting early: your team gets to choose when key milestones happen, rather than working around a compressed deadline. That matters for organizations juggling a busy performance or exhibition calendar, where a migration timed poorly can compete with other priorities.
Where To Start
A v16 migration doesn’t have to be disruptive if it’s planned properly. The right first step is a technical and organizational readiness assessment: auditing your current integrations, mapping your Contact Permissions structure, and validating your membership pricing rules before migration begins, not during it.
A good readiness assessment should leave your team with a clear picture of three things: what needs to be rebuilt, what needs to be reconfigured, and what can carry over as-is. That clarity is what turns a migration from an open-ended project into a scoped one.
iMedia has worked with arts and culture organizations through platform migrations like this one, and we know where the real friction points tend to show up. If you’re not sure where to start, or need support in identifying the digital implications, we can help you identify dependencies, prioritize the work, and build a plan around your timeline and the Tessitura deadline.