One important step is turn off user talk page Beta Feature for each opted-in users and then disable the Beta Feature permanently.

In T370722#10005410, @Bugreporter wrote:

One important step is turn off user talk page Beta Feature for each opted-in users and then disable the Beta Feature permanently.

Great spot, @Bugreporter. @Trizek-WMF and I will ensure this step is accounted for in the un-deployment sequence.

Thank you for saying something; if any other ideas of this sort emerge, we'd value you sharing them with us!

In T370722#10005410, @Bugreporter wrote:

One important step is turn off user talk page Beta Feature for each opted-in users and then disable the Beta Feature permanently.

It is already covered: T248309: StructuredDiscussions (Flow): Prevent users from enabling Flow on their user talk page (beta feature) :)

In T370722#10012556, @Trizek-WMF wrote:

In T370722#10005410, @Bugreporter wrote:

One important step is turn off user talk page Beta Feature for each opted-in users and then disable the Beta Feature permanently.

It is already covered: T248309: StructuredDiscussions (Flow): Prevent users from enabling Flow on their user talk page (beta feature) :)

What I mean is disable for people currently using it in user talk page.

Update

Today, @Trizek-WMF defined three deployment phases (see below). Next, Benoît is going to:

1. Assign each wiki where Flow is active (T350073) to one of these three un-deployment phases (see below)
2. Estimate how much time wikis in each un-deployment phase will need for the various steps within the un-deployment sequence (e.g. manually migrating Flow boards to sub-pages, enabling a script to mass-migrate Flow boards that had not been moved manually, etc.)

In parallel, I'll be working with Editing Engineering to estimate the time needed for doing things like writing a migration script, QA'ing said script, and addressing any issues that script surfaces.

Deployment phases