Overview

Chezie is upgrading to a new platform foundation this spring!

Over the last few years, Chezie has grown quickly, and we’ve reached a point where we need to invest in a stronger foundation to support the demands of our customers. This upgrade gives us the ability to improve performance and reliability, ship new features faster, and support more types of internal communities over time, not just ERGs.

This is a full platform migration, but for most users, the experience should still feel familiar. The goal here is not to force everyone to learn a completely new tool. It’s to move Chezie onto infrastructure that is more stable, more scalable, and better suited for where the product is going.

What’s new?

Here’s a quick rundown of some of the improvements that are coming with this migration:

1. Teams - Support for multiple types of communities

Chezie will no longer be limited to ERGs alone (though we will 100% continue to support ERGs). You’ll be able to manage different types of internal communities (for example: ERGs, interest-based groups, location-based groups, or other programs) within a single platform, with clearer structure and permissions.

2. Improved events and engagement workflows

We’re making meaningful improvements to events, including better invite management, more flexible event setup (including hybrid events!), and improved visibility into participation and engagement.

3. Faster performance and a more reliable foundation

Pages will load faster, exports will be more consistent, and the overall experience will feel smoother and more predictable. This foundation also allows us to move faster on reporting, approvals, and analytics going forward.

Migration Timeline

We’ve already started communicating about the platform upgrade and what customers can expect.

March-April 2026 (Done ✅)

We began sharing early updates with customers and IT teams about the upcoming Chezie platform migration, including what’s changing at a high level and which integrations will need to be reconnected later in the process.

Early May 2026 (In Progress)

We expect to begin with a small beta group of customers. The purpose of this phase is to validate data migration, integration reconnection, core workflows, and overall platform reliability before broader rollout.

Mid-to-late May 2026

We expect to begin broader customer migrations in phases. Each customer will receive a specific migration window, along with more detailed instructions for admins and IT teams.

Late May / Early June 2026

Most standard customer migrations are expected to be complete by this point, with any remaining edge cases or custom integrations handled separately.

Exact dates will be updated once our internal testing and beta testing commence. We’ll continue updating this page as the rollout plan becomes more concrete.

What Admins and IT Teams Need to Do

The goal is to make this migration as predictable and low-effort as possible. There’s nothing most customers need to do right away, but there are a few things to be aware of.

For Company Admins / ERG Owners

You should:

• keep an eye out for your migration window and any customer-specific instructions

• make sure the right IT contact is looped in for setup work if your organization uses SSO or calendar/video integrations

• review any updates we share about sign-in links, timing, or known migration-day changes

If your organization uses custom integrations, we’ll reach out directly with more specific guidance.

For IT Teams

Most customers will need IT involvement to reconnect the following in the new environment:

• Single Sign-On (SSO), which will migrate to SAML

• Calendar integration, either Google or Microsoft

• Video meeting integration, such as Zoom or Webex if used (MS Teams and Google Meet are handled with the Calendar integrations, so they do not need to be re-connected separately)

Your HRIS integration does not need to be migrated and requires no action as part of this transition.

We’re still finalizing a few migration steps through beta testing, so we’re intentionally holding off on publishing detailed integration setup guides until those flows are validated. Before your migration window, we’ll share the exact instructions your team needs.

What Changes During Migration

Each customer will be notified individually about their migration window. When your migration window arrives, there are a few practical changes to expect.

1. Your sign-in URL will change

Customers will receive a new sign-in URL for the new Chezie environment

Ex: chezie.app/company → company.chezie.app

2. Group URLs will change

Links to specific groups in Chezie will also change as part of the migration.

Ex: chezie.app/company/groupid → company.chezie.app/groupid

3. Some technical setup may happen during or around your migration window

If your organization uses SSO, calendar, or video integrations, your IT team may need to complete reconnection steps in the new environment before the migration is fully complete. We’ll share customer-specific instructions ahead of time.

4. Some event behavior may be affected

We are still finalizing a few migration details through internal and beta testing, but one known area we’re evaluating closely is how legacy events behave after migration. We’ll share customer-specific guidance in advance if any limitations apply to events created before your migration window.

Please note that each customer will receive a hard deadline to create events on the current Chezie platform. After that date, events will no longer be editable from within Chezie (but you can still edit them directly in your service account calendar, if need be).

FAQ