Bug 1433324 made activity stream the only about:home and about:newtab but migration tests were running only on old about:home and tiles about:newtab. See attachment for screenshot of differences between the manual migration on activity stream vs notification bar migration on tiles. I'm assuming we don't want both migration flows at the same time in activity stream. And perhaps there should only be the "auto migration" ? To just do the Tiles migration, we would need to remove the manual migration message and do something to show the notification bar: https://searchfox.org/mozilla-central/rev/d03ad8843e3bf2e856126bc53b0475c595e5183b/browser/modules/AboutNewTab.jsm#31-38 Although unclear if we should instead make the notification bar look more like the manual migration in-page prompt. It sounds like there's active development on the auto migration even though it's not shown by default to Firefox since 57 as activity stream is the default since then. dthayer, is there a timeframe for when auto migration should appear on activity stream? How should those look?

CCing Verdi in case he wants to chime in. Basically we're still just planning on experimenting with automigration in the future. Right now the work going into automigration is purely around migration performance, which will open up the opportunity to explore the user perception of automigration without the noise of it significantly janking the whole browser. Regarding design decisions about the undo bar, I can't speak too in depth. I don't think that the notification bar was going to be the final answer to the UI though, as I know Verdi has this mockup lying around: https://mozilla.michaelverdi.com/public/am6.framer/ I'd like to get more clarity on when we want to begin these experiments, but honestly I don't know when that will be. I would hazard a guess at 61 though.

Maria to follow up with Chris M. whether we need automigration and what experiments to run