---
title: "Migrating from Event Landing Pages to Portals"
slug: "migrating-from-event-landing-pages"
updated: 2026-04-16T19:11:39Z
published: 2026-04-16T19:11:39Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrating from Event Landing Pages to Portals

Event landing pages have been deprecated in favor of portals using the portal events widget.

The portal events widget maintains parity with existing event landing pages and adds additional customizations, like formatting, grouping, and combining multiple calendars, lists, or maps in a single page.

## The *Convert to Portal* tool

To generate a new event portal from an existing landing page, we’ve added a **Convert to Portal**tool to the event landing page popup. This tool automatically generates a portal from an existing landing page.

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/Convert to Portal.png)

This tool works best for relatively simple landing pages. If your landing page is complex, or needs extensive updates, creating a new portal is the better option.

> [!NOTE]
> 💡 Convert to Portal does not delete your original landing page.

## Generating an event portal from an existing event landing page

To automatically generate a portal from an existing landing page:

1. Go to **Database** → **Event Landing Pages (deprecated)**.
2. Select a landing page.
3. Next to **Convert to Portal**, select **Generate.**
4. Confirm the browser dialogue. You are redirected to the new portal.

The previous folder configurations are now part of the events widget.

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/New portal from landing page.png)

The new portal’s key is `<YOUR_PORTAL_KEY>_vNew`.

If the landing page had a key of `visit`, the new portal’s key would be `visit_vNew`.

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/New portal key.png)

### Portal key considerations

- Each portal key must be **unique**.
  - This is true across portals and event landing pages.
  - For example, there **cannot be** an event landing page with the key of `visits` and a portal with the key of `visits`.
- Portal keys have a **32-character limit**. If an event landing page key has more than 27 characters, it will exceed the 32-character limit when `_vNew` is appended, and the portal won't be generated.

## Replace an event landing page with an events portal

To replace an existing landing page with an events portal:

1. From the main navigation, select **Database.**
2. Select **Event Landing Pages (deprecated).**
3. Select a landing page.
4. Copy the key and paste it somewhere you can access it later.
5. Change the key to a placeholder value. For example, `visit-old`.
6. Select **Save.**
7. From the main navigation, select **Database.**
8. Select **Portals.**
9. Select an existing event portal—likely the one you’ve just generated with the [Convert to Portal tool](/v1/docs/migrating-from-event-landing-pages#the-convert-to-portal-tool)—or [create a new one](/v1/docs/event-portals).
10. Replace the portal’s key with the key of your landing page. For example, replacing `visit_vNew` with `visit`.

📖 [Import our sample event portals into your database](/v1/docs/event-portals).