> ## Documentation Index
> Fetch the complete documentation index at: https://learn.playlab.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Migrating to the new Playlab
> What changes during the migration to the new Playlab, what stays the same, and what to do before, during, and after.
This guide is for people coming from the previous version of Playlab. It will be retired in August 2026 once everyone has migrated. For current Playlab guidance, see [Learn on Your Own](/getstarted/Overview) or [Feature Documentation](/features/Overview).
Most Playlab orgs migrate with the Playlab team during a scheduled migration window. This page is the self-serve overview. It covers what changes, what stays the same, what to do before and after, and where to get help.
Larger orgs follow a coordinated migration with the Playlab team. The walkthrough on this page is for self-serve users on smaller orgs.
## What's actually changing
Playlab reorganizes how content and permissions work. The structure and workflow comparisons are documented in:
* [Navigating Playlab](/getstarted/Navigating%20Playlab)
* [Workflow cheat sheet](/whatsnew/Workflow%20Cheat%20Sheet)
The short version: org> workspace> app> collection becomes the explicit hierarchy. Sharing happens through a Share modal on each app. Activity is visible at workspace, member, and org levels. Collections enable curated bundles for partner deployment.
## What stays the same
Migration preserves what was already working. Your apps, workspace members, conversation history, references, and integrations all carry forward.
| Thing | What happens during migration |
| -------------------------------------- | ---------------------------------------------------------------- |
| Your apps | Carry over with the same prompts, references, and starter inputs |
| App owners | Preserved |
| Workspaces | Carry over with the same names, members, and apps |
| Workspace members | Preserved with mapped roles |
| Conversation history | Preserved and queryable |
| References (org, workspace, app level) | Preserved |
| Integrations (SSO, rostering) | Preserved |
| Activity history | Preserved |
| URLs and saved links | Old URLs continue to redirect to the current paths |
You do not lose work in migration. The structure of how content lives changes; the content itself does not.
## Where things moved
A short reference for the most-asked relocations.
| Previously | Now |
| ------------------------------ | ---------------------------------------------------------------------------- |
| Workspace> Members> Add Member | Workspace> Members> **Add Members** or **Create Invite Link** |
| Workspace> Apps> New App | Org or Workspace> **New App** |
| App> Publish> Pick visibility | App> **Share**> Publish toggle and visibility selector |
| Workspace> Activity | Workspace> Activity (workspace-segmented) or Org> Activity (cross-workspace) |
| Remix to deploy | App> **Share**> target org or **Add to Workspace** in another workspace |
| Curated bundles by remixing | Org> **Collections**> New Collection |
For the full mapping, see the [workflow cheat sheet](/whatsnew/Workflow%20Cheat%20Sheet).
## Migration walkthrough video
## What to do before migration
A short checklist:
* [ ] Note your active workspaces and the apps you care about
* [ ] If you have apps with shared collaborators, note who currently has edit access
* [ ] If your org uses rostering, talk to your IT contact about sync timing
* [ ] Schedule a 30-minute review session for the day after migration
* [ ] Bookmark the [workflow cheat sheet](/whatsnew/Workflow%20Cheat%20Sheet) for reference
If you have old URLs deeply embedded in class materials, those URLs continue to work. The redirects route them to the current equivalents.
## What happens during migration
Migration runs as a background process. The visible effects in your org:
* A short window (usually under an hour) where the org is read-only
* An announcement banner letting users know migration is in progress
* A welcome banner once migration completes, pointing to introduction materials
Members do not need to log out and back in. The next page load after migration shows the new interface.
## What to do after migration
A short checklist:
* [ ] Open your dashboard and verify your workspaces and apps are present
* [ ] Try sharing an app from the new Share modal to confirm the flow
* [ ] Set workspace building permissions for any classes you run (these are off by default)
* [ ] Review members in your workspaces and adjust roles if needed
* [ ] Read [What's new for Builders](/whatsnew/What's%20New%20for%20Builders), [What's new for Educators](/whatsnew/What's%20New%20for%20Educators), or [What's new for Admins](/whatsnew/What's%20New%20for%20Admins) depending on your role
If anything looks wrong, email [support@playlab.ai](mailto:support@playlab.ai). We can roll back individual issues.
## Help
For org admins on larger accounts, the Playlab team is the first point of contact and can walk you through the changes.
For self-serve users, [support@playlab.ai](mailto:support@playlab.ai) is the right starting point.
For role-specific overviews:
* [What's new for Builders](/whatsnew/What's%20New%20for%20Builders)
* [What's new for Educators](/whatsnew/What's%20New%20for%20Educators)
* [What's new for Admins](/whatsnew/What's%20New%20for%20Admins)
* [What's new for Networks or Districts](/whatsnew/What's%20New%20for%20Networks%20or%20Districts)
For honest context on what Playlab does not yet do, see [Known limitations](/whatsnew/Known%20Limitations).
## FAQ
Per-issue rollback is supported. We can revert specific apps, workspaces, or settings. Org-level rollback after migration is not supported.
Old URLs continue to redirect to the current paths. Bookmarks, saved links, and references in class materials should continue to work.
Roles map automatically to the current set — **Owner** (all-access), **Creator**, **Editor**, **Viewer**, and **Workspace-only**. Workspace leads keep their workspace-level roles (Owner, Facilitator, Participant).
Each org migrates as a unit. If your org has migrated, all your workspaces are on the new version. Cross-org sharing with a non-migrated org is supported during the transition window.
For most orgs, under an hour. Larger orgs with many workspaces and references may take longer. Your migration meeting is when this is scheduled.
Apps shared with them keep working. They see a small banner if they happen to open Playlab during the brief read-only window. No action required from them.
No. Apps, conversations, references, members, and activity history all carry forward. URLs redirect.
Yes. Migration windows are scheduled with the Playlab team. If you need to postpone, reach out to them. New orgs default to the new version starting May 2026.
***
Last updated: 06-26-2026
Contact us at [support@playlab.ai](mailto:support@playlab.ai)