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 introduces more flexible layouts, improved templates, clearer content structure, and stronger branding control across your intranet. From May 1, 2026, it will no longer be possible to create or edit pages in the legacy Happeo Pages editor. Existing pages will remain visible, but updates must be made through Pages 2.0.
To update a legacy page after May 1, migrate it to Pages 2.0, edit the draft in the new editor, and publish the updated version to make your changes visible. Migrating ahead of time helps ensure your team can continue updating content without interruption and keeps your knowledge accurate and up to date.
2. Before you begin
- 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. Prioritize your most actively used content first.
- Technical support for the legacy editor will be limited to critical issues only from May 1.
- Legacy pages will remain visible to employees after May 1, but cannot be edited until migrated.
đź—’ 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. What changes on May 1
- Creating page groups: The Create button will open the Pages 2.0 editor directly. It will no longer be possible to create a legacy page group.
- Editing pages: It will no longer be possible to enter the legacy editor to make changes. To edit a legacy page, migrate it to Pages 2.0 first.
- Changing permissions: Permission changes to legacy pages must be made through Pages 2.0. Migrate the page first, update permissions in the Pages 2.0 editor, and save. You do not need to publish for permission changes to take effect.
- Page group settings: Settings for legacy page groups cannot be changed until after migration. Any updates must be made in Pages 2.0 after migrating the page group.
- Page templates: Legacy page templates will no longer be available. Because it will not be possible to create new legacy page groups, V1 templates cannot be carried forward automatically. See Section 6 for how to recreate your templates before the deadline.
4. 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.
5. How to migrate a page to Pages 2.0
You can trigger a migration from view mode by clicking the Migrate button in the top right corner of the page. You do not need to enter the legacy editor to start a migration. Migration can also 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.
6. How to update permissions on a legacy page after May 1
From May 1, the legacy editor is no longer accessible for direct edits, including permission changes. To update who can access or edit a legacy page:
- Navigate to the legacy page.
- Click the Migrate button in the top right corner to create a Pages 2.0 draft.
- Open the Pages 2.0 draft and update the page permissions.
- Save your changes.
⚠️ Important: You do not need to publish the Pages 2.0 version for permission changes to take effect. Publishing will replace the legacy version and make any content edits visible to employees.
7. How to update page group settings after migration
Page group settings for legacy page groups cannot be changed until after migration. Once you have migrated a page group to Pages 2.0, you can update its settings in the Pages 2.0 editor as normal.
🔎 For guidance on how to manage a page-level permissions in Pages 2.0, see this article.
8. How to recreate your legacy templates in Pages 2.0
Legacy page templates cannot be migrated automatically. To carry your existing templates forward, recreate them in Pages 2.0 before May 1.
The recommended approach is:
- Create a new legacy page group using the V1 template you want to preserve.
- Migrate that page group to Pages 2.0.
- Use the migrated version as the basis for a new Pages 2.0 template.
🔎 See this article for detailed instructions on how to create Pages 2.0 templates.
This must be completed before May 1, after which it will no longer be possible to create new legacy page groups or access V1 templates.
⚠️ Important: Templates are not transferred automatically during migration. Review which templates your organization relies on and recreate them before the deadline.
9. 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.
10. Frequently asked questions
Will my legacy pages be deleted after May 1?
No. Legacy pages will remain visible to anyone with access, but they cannot be edited in the legacy editor. To update a page after May 1, migrate it to Pages 2.0 first. Once you publish the Pages 2.0 version, it replaces the legacy version and your updates become visible to employees.
Can viewers still access legacy pages after May 1?
Yes. Legacy pages remain visible to anyone with access. Only editing is restricted until the page is migrated.
Can I change who has access to a legacy page after May 1?
Not directly in the legacy editor. You need to migrate the page first, then update permissions in the Pages 2.0 editor. You do not need to publish the new version for permission changes to take effect. See Section 6 for full steps.
Can I change page group settings for a legacy page group after May 1?
Not until after migration. Any page group settings that need updating must be made in Pages 2.0 after migrating the page group. See Section 7.
What happens to my legacy page templates?
Legacy page templates will no longer be available from May 1. Templates cannot be migrated automatically. Before the deadline, recreate any templates you rely on in Pages 2.0 using the approach described in Section 8.
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. Prioritize your most actively used content first. One exception: if you rely on legacy page templates, these must be recreated before May 1, as V1 templates will no longer be accessible after that date.
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.