Migrating
What does a migration not bring?
Theme code, plugins, and anything a plugin kept in its own tables do not come across. A WordPress site leaning on a dozen plugins is not one export. It is a decision about which of those twelve behaviours the new site genuinely needs. Content, media and structure move. Bespoke template code does not.
Theme code and plugins
Neither comes across. Templates are rebuilt as components and plugin behaviour has to be replaced by something, which is a decision rather than an import.
The good news is how much of the usual plugin list is already in the product. Forms, SEO fields, redirects at the path level, a media library, roles and approval workflow are not plugins here.
A twelve plugin site, honestly
Take a WordPress site with twelve active plugins. Four are usually already covered by the product. Three turn out to be doing nothing anybody remembers asking for. Two are doing something real that needs a genuine replacement. Three are keeping data in their own tables and need an export before the site is switched off.
That triage is the migration. The import is a Tuesday.
What that means for the timeline
Budget the time for the decision list, not for the transfer. Teams that plan a migration as a data exercise are the ones who discover in week three that nobody knows what the events plugin was for.
Also in migrating
Still have a question left
Thirty minutes with the product team, and a straight answer.