Start with low-risk pages, involve page owners early, and edit and review upgraded pages before clicking the complete move button.

For larger organizations, use a phased upgrade approach: prepare critical pages, review customizations, and train editors. Then upgrade gradually, prioritizing high-impact content.

Classic Editor and Content Designer coexist during the transition. Contact your Customer Success Manager or Staffbase Support for more information.

No. The upgrade follows a deterministic, rule-based approach.

Not yet. Only pages marked as ready can be moved.

Pages using unsupported blocks, heavy customizations, or complex nesting structures may not be eligible in early phases. Staffbase is expanding support for more page types over time.

Yes. The Ready for Content Designer tab lists all pages that are ready for upgrade.

Complex pages can be upgraded, but eligibility depends on their structure and product development state on the new Content Designer capabilities. Deep nesting and legacy widgets may affect readiness.

After you confirm the move, the upgraded page replaces the Classic version, no duplicate page is created, and the page's ID, URL, and settings stay the same. If the page was already published, the new design becomes immediately visible to employees.

Yes. Both editors currently coexist, and upgrades happen on a page-by-page basis. Since Q2 2026, the Content Designer is the default editor for new pages. Creating a new Classic page requires explicit opting in.

For the phase-out timeline, refer to Classic Page Editor Retirement Timeline.

Not immediately. Classic Editor and Content Designer coexist today, and you can opt in to the Classic Editor or upgrade at your own pace using the upgrade tool. Staffbase is gradually phasing out the Classic Editor as a transition to the Content Designer.

Once a page is upgraded to the Content Designer, you can customize it using the dedicated Content Designer tab in Custom CSS. The Content Designer uses a documented set of stable selectors designed to remain compatible with future product updates.

Custom CSS written for classic pages is not automatically carried over, as Content Designer pages use a different rendering system. If you have heavily customized environments, such as multibranding, review your current CSS before the upgrade and plan to recreate the necessary styles in the Content Designer tab.

Yes. Page status, visibility, and analytics continuity are maintained during the upgrade.

If you have opted out of the Content Designer for Pages, you don't have the move option available. The Upgrade tool is also currently visible to administrators only, and not all pages are ready to be upgraded yet.