The biggest, most consistently visible gains are in branching, quality scans, and large content and bundle operations, the workflows that tend to slow teams down most as a content library grows. There are various subtle quality-of-life improvements included as well, such as no longer needing to re-save a file after you create the target of a broken link, making edits and uploads even faster.

There are also API improvements made available with this new infrastructure: localization REST APIs, and commit-scoped file changes, which let you group related file changes into one commit with a single commit message.

You'll also be on the platform receiving our forward-looking investment, including new capabilities that aren't feasible to build on the legacy stack.

Yes, we do. These are from internal testing and our first production migrations:

Significantly. Today, most fixes and improvements wait for a scheduled maintenance window with roughly 4 hours. After this migration, most updates can be rolled out in about 15 minutes with far less disruption, so issues get resolved faster and new capabilities reach you sooner.

Both. Immediately, it improves day-to-day performance. Strategically, it's the foundation our future roadmap is being built on, including improved search, expanded APIs and governance features, better localization/packaging workflows, and significant capabilities for supporting agentic workflows.

There are many enhanced features with this upgrade, for example, enhanced search, including creating saved views for easy access later. One important aspect of this upgrade is laying the groundwork that enables us to build and deliver valuable features that just weren't possible before.

For more new features, see It's just the beginning!.

With the exception of a few areas, all functionality that was available on the previous infrastructure will remain available on the NextGen Infrastructure.

• XQuery-based reports and assignment triggers are being retired in favor of using the new features and APIs that provide the same or more functionality. If your team has custom or specialized reports, our team will reach out to you ahead of your migration to help you move to the new capabilities.

• The Recently Edited view (previously Recent) is now limited to 90 days or 1,000 records (whichever is hit first).

• The Trash UI and left navigation have been removed from the Content Library in favor of a more robust ability to access deleted files in the Activity interface under the Trashed Documents filter.

In most cases, nothing. We'll reach out directly if anything needs to happen on your end beforehand.

The usual support channel: support.heretto.com. Just flag that it's related to your recent migration so it gets prioritized appropriately.

Your support channel and Heretto contacts remain the same.

Yes. Your Customer Success Manager (CSM) will follow up after the migration to confirm everything is running smoothly and to answer any remaining questions.

Your Customer Success Manager (CSM) is the best point of contact for questions specific to your migration and timeline. We're also happy to set up a short call to walk through anything in this FAQ in more detail.