Pages 2.0 | How to Migrate Pages

Audience: This article is for Happeo customers with existing content in the old Happeo Pages editor who want to move their content into the new Happeo Pages experience, known as Pages 2.0. To learn how to create new pages in Pages 2.0, see here.

Beta information: The Pages 2.0 Migration Tool is in managed beta with selected early adopters. Full availability for all customers is planned for October 2025. If you have questions about when migration will be available for your organization, contact your Customer Success Manager.

For a comprehensive list of Pages 2.0 articles, visit this page.

The benefits of Pages 2.0

Migrating to Pages 2.0 isn’t just a technical upgrade – it’s a chance to give your intranet a fresh start on a more modern, reliable foundation. Pages 2.0 is built to help your team work faster, create more consistently, and deliver a better experience to end users.

Here’s what you gain by making the move:

• Better technology – Built on React, Pages 2.0 replaces legacy systems with a stable, future-proof foundation that adapts as your needs grow.
• Future-proofing – All new features, performance improvements, and enhancements will be delivered to Pages 2.0 first.
• Faster to load – Smoother, more responsive navigation and reduced loading times for your users.
• Faster to build – A more intuitive editor, enabling your team to create and refine pages quickly.
• Easier to maintain – Bugs and issues can be identified and resolved faster, keeping your intranet reliable.
• Open-source advantage – Leveraging widely adopted open-source technology means we can implement best practices, respond faster, and deliver ongoing improvements.
• Consistent branding – Brand Styles apply your organization’s colors, fonts, and styles across Page Groups. Combine with Page Group, Page, and Section Templates to keep your intranet polished and consistent without adjusting each page manually.

Before you start migrating

1. Set up a Brand Style

Your Brand Style controls your organization’s colors, typography, and element styles in Pages 2.0. Setting it up before migrating ensures every page you move automatically reflects your brand identity without the need for manual adjustments.

If no Brand Style is set, Pages 2.0 will temporarily apply Happeo’s default branding until you create and activate your own. Once activated, your Brand Style will instantly apply to all migrated and newly created Page Groups in Pages 2.0.

You may also want to set up Page Group, Page, and Section Templates at this point. While not essential for migration, they make it easier for users to create consistent new content from scratch. Learn more.

Admins or users with the branding permission can create and manage Brand Styles from Admin Settings. Page Group Owners and Page Group Editors can change Brand Styles within the Pages 2.0 editor if more than one style exists. Learn more.

2. Understand your content

Before moving anything, know exactly what you have.

A complete inventory helps you decide what to keep or archive – and gives your team a shared reference for the entire migration project.

To export your inventory:

1. Open Admin Settings.
2. Go to Page Groups.
3. Select Export in the top right.
4. Choose All active pages export.
   • If the file doesn’t download, disable any ad blockers.

This export includes all non-archived pages (published and unpublished) plus ownership details for each Page Group. Use the file to:

• Identify Page Groups without Owners or Editors
• Allow Page Group Owners and/or Editors to highlight outdated or duplicate Page Groups that can be archived
• Highlight high-impact areas to prioritize or select low-risk areas for early trial migrations.

Before you migrate, you may want to archive Page Groups – such as duplicates or ones that are no longer relevant. This will save you time during your migration process.

How to migrate to Pages 2.0

The migration tool lets you move individual Pages, Subpages, or entire Page Groups to Pages 2.0 in just a few clicks. When you migrate, a draft is created in the Pages 2.0 editor so you can review and refine it without affecting your live content. The original version in the old editor remains visible to viewers until you publish the new draft.

You can start the migration from three different places:

1. While viewing a page.
2. While editing a page.
3. From the Page Groups section in Admin Settings.

Note: To migrate content, you must be a Page Group Owner, Page Group Editor, an Admin, or have Admin mode enabled by selecting your avatar and expanding the menu.

Language settings: If no primary language is set in the original page group, the migrated page will default to English. To avoid incorrect language settings, we recommend setting a primary language in the legacy page editor before migrating.

Option 1: From viewing a page

1. Navigate to the page or page group you want to migrate.
2. Click Migrate in the top-right corner of the page editor.
3. Choose one of the following:
   • Single Page Migration: Migrate only the page you’re currently viewing.
   • Page Group Migration: Migrate the entire group, including all subpages.
4. Click Next and review the confirmation message.

Option 2: From editing a page

1. Open the page or page group you want to migrate.
2. Click the Edit icon in the top-right corner to enter the page editor.
3. In the Page settings menu, scroll to the bottom and click Migrate.
4. Choose either:
   • Single Page Migration: Migrate only the page you are editing.
   • Page Group Migration: Migrate the entire group, including all subpages.
5. Click Next and review the confirmation message.

Option 3: From the Admin Settings

1. Click your avatar in the top-right corner of the main navigation and select Admin Settings.
2. Go to Page Groups and click on the page group you’d like to migrate. Any page groups that still use the legacy editor will have a V1 tag.
3. At the top, you’ll see a banner message: “Some pages in this page group use the old editor. Migrate and publish all pages in Pages 2.0 editor.” Click Migrate within that message.
4. Select either:
   • Single Page Migration: Migrate only the page you’ve selected.
   • Page Group Migration: Migrate the entire group, including all subpages.
5. Click Next and review the confirmation message.

Finalizing migration

• If a page contains unsupported widgets, placeholders will appear after migration. These can be replaced or adjusted in Pages 2.0 to align with your design. Learn more about unsupported widgets.
• Click Start Migration to begin.
• Migration takes under a second for individual pages but may take a few minutes for larger page groups.

Tip: We recommend migrating full page groups rather than individual pages. This keeps your intranet navigation consistent, ensures branding is applied evenly, and makes the review process much smoother.

Once complete, you’ll be taken directly to your Pages 2.0 drafts for review, where you can polish layouts, adjust content, and publish when ready.

Managing drafts in Pages 2.0

Now that draft versions of your content have been created, you can review your migrated content. All supported widgets and their content will carry over, ensuring a smooth transition. This includes both the widget itself and the content within it. For example, text in a Text Widget will remain intact in the new draft version. 

Unsupported widgets will be automatically replaced with placeholder widgets, which you can simply replace or delete as needed. This occurs if the widget has been deprecated and will not exist in Pages 2.0, or if the widget is still in development. Learn more about widget parity.

Unpublished vs. published drafts

Unpublished drafts are versions of your pages visible only to you and editors of that page or page group. You can access and edit these drafts in draft mode. Changes made in draft mode are automatically saved. However, for these page groups or pages to be visible to the rest of your organization (viewers), you must publish them. Learn more.

Refining & publishing 2.0 drafts

Before publishing your migrated pages, it’s a good idea to check whether everything looks as it should. Here are some key areas to review and refine to suit your needs:

1. Sections and widgets: Check how your widgets have migrated, and replace or delete placeholders of unsupported widgets with alternatives. You can also adjust widget placements to optimize readability and usability. For a full list of widgets that have been relocated or deprecated, see here.
2. Brand consistency: Verify that your migrated fonts, colors, and elements have inherited the brand style you previously set up and activated within the Admin Panel. You can also opt to change the branding of your pages if you have more than one brand style set up. Learn how.
3. Content and resources: Double check that the information on your page is still relevant and accurate, such as switching out old versions of files within Link Lists or File Widgets (for example, policies or access guides).
4. Optimize for Happeo Search: Use our new AI Page Analysis functionality to receive actionable recommendations to boost the findability, readability, and accessibility of your content. This is particularly important for identifying content through Happeo Search. Learn more.
5. Preview: Preview how your pages will look. Stretch and shrink your internet browser window to check responsiveness, and assess mobile responsiveness by testing on different screens. Perhaps a colleague may also help by reviewing pages to check for any missed refinements.

Note: While we recommend editing the draft version in the Pages 2.0 editor, it is possible to switch to the live version and edit within the old editor instead. However, any changes to the live content will not be reflected in the draft version that you previously migrated. To switch to the old editor, click the Live button at the top of the page editor and click Edit old version.

Publishing 2.0 drafts

Once you’re happy with the new 2.0 draft(s), publish to promote it to live status – replacing the original version in the old editor. Publishing a draft will make it visible for all viewers (and editors) of the page, making it discoverable through search and the Pages navigation found in your intranet’s main navigation.

There are several ways to publish pages in Pages 2.0. You can:

• Publish individual pages or subpages
• Publish multiple pages or subpages
• Publish all pages and subpages

As best practice, we recommend publishing all pages within a page group together once they’re ready. This ensures consistent branding and smooth navigation. Publishing only some pages won’t cause errors but may create visual or navigational inconsistencies. 

Learn more about publishing options.

Note: Published pages and subpages will be indicated by a green dot to the left of their name, replacing the orange dot used for noting unpublished pages and subpages.

Reverting a published draft

After publishing a converted page, you can revert to a previous version and edit it within the Pages 1.0 editor using Happeo's page history functionality.

1. Go to the page you want to revert to a previous version.
2. Click the pencil icon at the top-right to enter the page editor.
3. Select Settings from the menu on the left.
4. Click Discard draft and go back to V1 editor.

You will then be taken back to the Pages 1.0 editor and your previous page version will be restored.

FAQs

When is the right time to migrate?

The migration tool will be available to all customers from October 2025. This gives you time to begin moving content into the new editor ahead of deprecating the original version of Happeo Pages.

How long do I have to migrate my pages?

When the migration tool becomes available, you will be able to make the transition at your own pace. However, it’s important to note that support for the original version of Happeo Pages will gradually wind down. To understand the timelines, please see below.

From H2 2026, any remaining content in the original version of Happeo Pages will be automatically migrated by Happeo – ensuring everyone is on Pages 2.0 before the original version is decommissioned. We’ll give ample notice, share regular updates, and provide clear guidance at every step.

Do I have to migrate everything at once?

No. You can migrate in stages — either page by page or group by group — depending on what works best for your timeline and resources. Many customers start by migrating lower-priority content first to get comfortable with the process.

How does migration work?

The migration tool allows you to move entire Page Groups or individual Pages into the new editor. When you migrate, the system automatically creates draft clones of your existing content in Pages 2.0, while your published versions remain live in the old editor. You can then review the drafts, refine them where needed, and publish when ready. Publishing is the final step that completes migration — once you publish, the content in the old editor is replaced by the new version.

How long does it take to migrate?

The technical migration is almost instant. A page or subpage can be converted into a draft in less than a second, while a full Page Group may take several minutes depending on its size. The time needed to review and refine drafts is more variable, ranging from a few minutes to half an hour depending on how polished the original content is and how many changes you’d like to make.

What are the benefits of creating drafts in Pages 2.0?

This approach to migration ensures flexibility and minimizes disruption. Your original content stays live while drafts are created in the new editor, so you can experiment without risk. Drafts give you the chance to review and adapt content before publishing. Once you publish, the transition is seamless — the draft simply takes the place of the old version, without downtime or duplication of work.

How similar is the content when migrated?

Migrated pages will look very close to how they appeared in the old editor. You may notice minor layout differences, often due to deprecated widgets or adjustments to your default Brand Style, but these are straightforward to correct during draft review.

What happens if I update the original content while a Pages 2.0 draft exists?

When you migrate a page, two versions exist independently: the draft in Pages 2.0 and the live version in the old editor. You can still edit the old version for a period of time, but any changes made there will not carry over into the draft. To keep content consistent, we recommend making updates in the Pages 2.0 draft instead and then publishing it, which will replace the old version.

Can I migrate the same page multiple times?

No. Only one draft can exist at a time. If you need to start over, you must discard the existing draft before migrating again from the original content. Please note that discarding is only available for individual pages, not entire Page Groups.

What happens if I discard a draft?

If you discard a draft, it cannot be recovered. Your live page in the old editor remains unchanged, so you can migrate it again to generate a new draft in Pages 2.0.

Can I undo a migration after publishing?

No. Once a draft is published in Pages 2.0, it replaces the old version. If you need to restore previous content, you can either unpublish and edit the new version or recreate the content from backups.

Can I have content from both editors in the same Page Group?

Yes, this is possible using single-page migration. However, we recommend migrating entire Page Groups together to keep navigation smooth and consistent.

What happens to content in multiple languages?

If you have pages in multiple languages, migration will carry over all language variants into the new editor. If you plan to change the primary language of a Page Group, we recommend publishing all existing variants first, then making adjustments afterwards.

What happens to widgets during migration?

As long as a widget exists in Pages 2.0, both the widget and its content will transfer. For example, text in a Text Widget will carry over, and colleagues listed in User Cards will remain in place. Some widgets, however, have been deprecated and will appear as placeholders in the draft. These can be reconfigured manually. The Breadcrumbs widget is no longer supported as a standalone widget and instead appears as a Navigation setting.

What if a page contains widgets that aren’t supported?

If a page includes unsupported widgets, the migration tool will notify you with a detailed list before proceeding. You can then choose to cancel or continue. If you continue, placeholders will appear where those widgets were, allowing you to make adjustments in the draft.

Will links still work after migration?

Yes – all files, links or URLs you use within your content will continue to work. 

Who can migrate?

By default, Page Group Owners, Page Group Editors, and Admins (when admin mode is enabled) can migrate content. Once a page or group has been migrated, the same access and sharing rights are retained, so editors can immediately begin updating the new versions in Pages 2.0.

Who can see migrated and published content?

When content is published in the new editor, everyone who previously had access will continue to see it. Permissions can be updated at any time from the editor.

Will page permissions carry over after migration?

Yes. When content is migrated to Pages 2.0, owners, editors, and viewers are carried over with their existing permissions, so access settings remain the same. Only users with access to Pages 2.0 (through beta, early access, or from the official release onward) will be able to view content published in the new editor.

Note: The “page author” field will be deprecated. Author information will be migrated into Pages 2.0 but will no longer be visible.

How can we track which content is in which editor?

Admins can visit the Page Groups section in Admin Settings and use new filters to track migration progress. Page Groups that still contain content in the old editor will display an “Original” tag. If migration has been started but drafts are not yet published, a “Migrating” tag will appear. Once drafts are published in Pages 2.0, no tag is shown — indicating the content now lives fully in the new editor.

What happens to analytics when content is migrated?

When a page is migrated, its analytics from the old editor are seamlessly combined with new data in Pages 2.0. This ensures you have a unified, continuous view of page performance, with no gaps or reporting errors during the transition.

Troubleshooting

What happens if I exit out of the page editor while reviewing a Pages 2.0 draft? How can I get back to it?

You can navigate back to the page editor by revisiting the original page and clicking the ‘Edit draft in Pages 2.0’ button in the top-right corner.

Alternatively:

1. Go to the original page and click the edit icon in the top-right corner.
2. In the Page Settings tab, click ‘Edit draft in Pages 2.0’.

What happens if I delete/discard Pages 2.0 draft?

When you migrate a page to Pages 2.0, a draft version of the original content is created. If you delete this draft, it cannot be recovered. However, your live (original) page in Pages 1.0 remains unchanged, so you can migrate it again to generate a new draft in Pages 2.0.

Can I migrate the same page multiple times to create several drafts?

No, only one draft can exist at a time. If you need to start over with a new draft, you must first delete the existing one and then migrate the page again from Pages 1.0.

Can I undo an accidental migration?

If you migrate a page but haven’t published it yet, you can delete the Pages 2.0 draft and re-migrate from the original version. If you have already published it, you can use Page History to restore the previous version. Learn more. 

What if the migrated page has unsupported widgets?

If your page contains widgets that are not compatible with Pages 2.0, you will need to replace them with supported widgets or adjust the section to fill in the gap left from removing the widget.

For guidance on finding and using compatible widgets, please refer to these articles:

• (Pages 2.0): Add and Manage Widgets
• (Pages 2.0): Page Widget Comparison Guide

Can I edit live page content when a Pages 2.0 draft exists?

If you have already auto-generated a draft in the Pages 2.0 editor, but have yet to publish the draft, you can still access and modify the original published Pages 1.0 version of the page. Here's how:

1. In the Pages 2.0 editor, click Live at the top of the page.
2. Click Edit old version. This will open the original Pages 1.0 editor.
3. Make the necessary changes to the content within the Pages 1.0 editor.
4. Click Save to apply your changes.

Important notes:

• By early 2026, editing in the original editor will no longer be possible. Attempts to edit will trigger automatic migration to Pages 2.0.
• Any changes made to the live content in Pages 1.0 while a draft exists in Pages 2.0 will not be applied to the existing  2.0 draft version of the page.