Uploaded February 2026 | Updated September 2026, 3 weeks ago
This video is a companion to our Legacy Editor migration overview and is designed specifically for in-house teams using Webflow.
👉 If you haven’t already, we strongly recommend watching the overview first:
youtu.be/_Xh47aAWehg
In this walkthrough, we’ll explain exactly how the legacy Editor deprecation impacts in-house teams — including what legacy Editor users are migrated to, how limited seats and roles work, and what to expect at each stage of the migration timeline.
We’ll also walk through practical scenarios to show how different Workspace plans, pending invites, and legacy Editor usage affect your migration.
Chapters
00:00 — Intro and who this video is for
00:22 — What legacy Editor users are migrated to
00:44 — Limited seats and roles explained
01:20 — Migration timeline for in-house teams
01:33 — February milestone: no immediate changes
02:41 — May milestone: automatic migration begins
02:51 — August milestone: legacy Editor retirement
03:27 — Scenario 1: You have pending legacy Editor invites at the time of migration
05:37 — Scenario 2: You fill all legacy Editor spots before migration
07:10 — Migration resources and next steps
Migration resources
Your primary source of guidance during this transition is the Legacy Editor Migration Hub, which includes FAQs, timelines, migration guides, and updated Webflow University content.
👉 Legacy Editor Migration Hub:
webflow.com/legacy-editor-migration
✨ Be sure to review the In-house teams and Team members sections for guidance tailored to your setup: webflow.com/resources/migration-guide/admins
This video pairs with:
▶️ Legacy Editor migration overview (watch first):
youtu.be/_Xh47aAWehg
▶️ Migrating from the legacy Editor: Freelancers and agencies
youtu.be/errjy_fw988
----------
Get started with Webflow: wfl.io/2r7cVUW
Join the Webflow Community: webflow.com/community
webflow.com
university.webflow.com
https://x.com/webflow
instagram.com/webflow
tiktok.com/@webflow
facebook.com/webflow
This video is a companion to our Legacy Editor migration overview and is designed specifically for in-house teams using Webflow.
👉 If you haven’t already, we strongly recommend watching the overview first:
youtu.be/_Xh47aAWehg
In this walkthrough, we’ll explain exactly how the legacy Editor deprecation impacts in-house teams — including what legacy Editor users are migrated to, how limited seats and roles work, and what to expect at each stage of the migration timeline.
We’ll also walk through practical scenarios to show how different Workspace plans, pending invites, and legacy Editor usage affect your migration.
Chapters
00:00 — Intro and who this video is for
00:22 — What legacy Editor users are migrated to
00:44 — Limited seats and roles explained
01:20 — Migration timeline for in-house teams
01:33 — February milestone: no immediate changes
02:41 — May milestone: automatic migration begins
02:51 — August milestone: legacy Editor retirement
03:27 — Scenario 1: You have pending legacy Editor invites at the time of migration
05:37 — Scenario 2: You fill all legacy Editor spots before migration
07:10 — Migration resources and next steps
Migration resources
Your primary source of guidance during this transition is the Legacy Editor Migration Hub, which includes FAQs, timelines, migration guides, and updated Webflow University content.
👉 Legacy Editor Migration Hub:
webflow.com/legacy-editor-migration
✨ Be sure to review the In-house teams and Team members sections for guidance tailored to your setup: webflow.com/resources/migration-guide/admins
This video pairs with:
▶️ Legacy Editor migration overview (watch first):
youtu.be/_Xh47aAWehg
▶️ Migrating from the legacy Editor: Freelancers and agencies
youtu.be/errjy_fw988
----------
Get started with Webflow: wfl.io/2r7cVUW
Join the Webflow Community: webflow.com/community
webflow.com
university.webflow.com
https://x.com/webflow
instagram.com/webflow
tiktok.com/@webflow
facebook.com/webflow
