Pages 2.0 is the new standard for creating and managing content in your platform. This article explains what the legacy editor deprecation means for your organization and how to migrate your existing pages before May 1, 2026.
🎯 Who this article is for: Admins, page group owners, and editors who manage content across the platform.
💼 Package requirements: Available on all plans.
1. Overview
Pages 2.0 brings more flexible layouts, better templates, clearer content structure, and stronger branding control to your platform. From May 1, 2026, it will no longer be possible to create or edit pages in the legacy Happeo Pages editor. Migrating ahead of time ensures your team stays uninterrupted and your knowledge remains accessible and up to date.
2. Before you begin
- From May 1, all new page groups must be created in Pages 2.0.
- Pages that remain in the legacy editor after May 1 will still be accessible to viewers, but cannot be edited until migrated.
- You need to be an admin, page group owner, or editor to identify and migrate legacy pages.
- Migration can be done at the page group or page level, so it helps to prioritize your most actively used content first.
- Technical support for the legacy editor will be limited to critical issues only from this date.
🗒 Note: The migration video series is a useful companion throughout the process, covering how to prepare, plan, and work through each stage of migration.
3. How to identify pages that need migration
Admins can get a comprehensive overview of their platform pages. Here’s how:
- Click your avatar from your platform’s main navigation.
- Go to Admin Settings.
- Navigate to the Page Groups section.
- Click Quick Filters to filter your pages.
- Look for pages tagged with V1. These are your legacy editor pages that are ready for migration.
- Review the list and note which page groups contain the most critical or frequently accessed content.
🗒 Note: You can use the Export CSV option in the top right corner to download a list of the Pages section. This helps you plan and track your migration progress.
🔎 To learn more about how V1 tags work, and what the experience is as you begin to migrate, visit this article.
4. How to migrate a page to Pages 2.0
Migrating your pages to Pages 2.0 can be done at the page or page group level from your Admin Settings. Once migrated, your content will take advantage of Pages 2.0's improved layout and templates.
🔎 For detailed steps on completing your migration, see How to Migrate Pages.
5. We’re here to help
Join the Pages 2.0 Community Channel to get support, share questions, and learn from others going through the same process. You can also reach out to your Customer Success team directly if you need hands-on help with your migration.
6. Frequently asked questions
Will my legacy pages be deleted after May 1?
No. Legacy pages will remain accessible to anyone with existing access. They simply cannot be edited until migrated to Pages 2.0.
Can viewers still access legacy pages after May 1?
Yes. Legacy pages remain visible to anyone with access regardless of their editor status. Only editing is restricted until the page is migrated, including access-level permissions.
Does everything need to be migrated by May 1?
No. May 1 marks the start of the legacy editor deprecation, not a hard deadline for full migration. Legacy pages will remain accessible, but cannot be edited until migrated. We recommend prioritizing your most actively used content first.
What happens to technical support for the legacy editor after May 1?
Support for the legacy editor will be limited to critical issues only. For the best experience and full support coverage, we recommend migrating before the deadline.
When will the legacy editor be fully deprecated?
We plan to fully deprecate the legacy editor in 2027. We'll keep you informed as the timeline progresses.