FAQs

Why is Chezie making this change?

We’ve outgrown the infrastructure Chezie was originally built on. This upgrade gives us a stronger foundation for performance, reliability, and future product development. It also helps us support more types of internal communities over time.

Will the platform look completely different?

No. The platform should still feel largely familiar. This is primarily a foundation upgrade, not a full reinvention of the user experience.

Will there be downtime?

Our goal is to make the transition as seamless as possible by deactivating customer’s old platforms and activating new ones in sync. However, this will be confirmed during internal and beta testing. More details on timing and exact downtime will be shared as we perform this testing.

As of now, no downtime is anticipated, as this is a new application launch. The transition will happen simultaneously — the new app will be enabled and the old one disabled over the weekend. If testing reveals that any migration downtime becomes necessary, we will notify you in advance.

Will our data be migrated?

Yes. The migration includes customer data such as members, groups, event history, budgets, communications, and related records. Data validation is one of the main goals of our testing and rollout process.

Will we need to reconnect integrations?

Most customers will need to reconnect SSO, calendar, and video meeting integrations in the new environment. HRIS integrations do not need to be migrated.

Does IT need to be involved?

Yes. We’ll need to work with your IT team to reconnect integrations in the new environment and support any setup or validation steps during migration. Please have your IT partners connect directly with us during the migration window so we can coordinate with them in real time.

Does our HRIS integration need to be migrated?

No. HRIS integrations do not require action as part of this migration.

Will our login URL change?

Yes. Your sign-in URL will change as part of the migration, and group URLs will change as well.

How will we know when it’s our turn to migrate?

We’ll contact your team directly with your migration window and any required next steps before your migration begins.

Are the dates final?

Not yet. We’re still finalizing details through internal testing and beta testing. This page will be updated as dates become more concrete, and each customer will receive direct communication ahead of their migration window.

What if our company uses a custom integration?

We’ll communicate directly with customers using custom integrations or edge-case setups, since those may require a slightly different migration path.

What support will be available during migration?

We’ll share customer-specific instructions ahead of your migration window, including what admins and IT teams need to do and who to contact with questions. We’re holding off on publishing detailed setup guides until those flows are validated through beta testing.

What attributes are required in the SAML assertion?

Only three attributes are needed: first name, last name, and email. These should match the configuration of your existing SAML application.

Will SSO be tested in both non-production and production environments?

Testing will be conducted in the production environment. However, access to the new platform will be restricted to admins only until it is fully opened to the rest of the company.