Start with low-risk pages, involve page owners early, and edit and review migrated pages before completing migration.

For larger organizations, use a phased migration approach: prepare critical pages, review customizations, and train editors. Then migrate 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. Migration follows a deterministic, rule-based approach.

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

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 migration.

Complex pages can be migrated, but eligibility depends on their structure. Deep nesting and legacy widgets may affect readiness.

Migration is validated against real enterprise pages, including complex scenarios.

After you confirm the migration, the migrated 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 migration happens 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 Will we be forced to migrate?

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

Once a page is migrated 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 migration and plan to recreate the necessary styles in the Content Designer tab.

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

If you have opted out of the Content Designer for Pages, you don't have the migration option available.