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

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

Classic and Modern editors coexist during the transition. Contact your Customer Success Manager or Staffbase Support for more information.

No. Migration follows a deterministic, rule-based approach.

Not initially. Pages using unsupported blocks, heavy customizations, or complex nesting structures may not be eligible in early phases.

Only pages marked as ready can be migrated.

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, and complex scenarios are included in the Beta validation process before broader rollout.

After confirmation, the migrated page replaces the Classic version. No duplicate page is created.

Yes. During the transition period, both editors coexist. Migration happens page by page, and the Classic Editor remains available in early phases.

No. Migration is not mandatory during the Beta phase. A full migration timeline will be defined later.

Customization compatibility is currently under review. Some CSS flexibility may be reduced to ensure long-term system stability.

Enterprise configurations, such as multibranding, should be reviewed early. Staffbase recommends identifying highly customized environments before migration planning.

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