Any starting tools or advice for a Bedrock > Standard WP build migration?

radicle
1

After running the radicle stack for awhile, I’m dreading going back to my legacy agency on FlyWheel with standard WP. I also dread to even consider what a migration tool might look like. All my plugins are backward-compat and don’t have to rely on Laravel / Sage / Composer.

There’s definitely a manual step-by-step DB/media process I could do, and potentially mock up a one-click migration MVP with the robot overlords, but has anyone found a better solution? Or any advice?

@ben / Roots team, I know how out of scope that might be but the radicle stack could explode in popularity if you had a migration tool from standard WP.

2

This is a guide for Bedrock, not for Radicle, that uses Lithify:

You’d need to use dev-main at the moment to have it work with WP Packages (needs a new tag for WP Packages support /cc @MWDelaney)

It would need some minor adjustments to work with Radicle. It’s possible we could bring this under the Roots org and support both stacks.

3

Classic user, doesn’t search the docs first… (I searched the forums at least lol).

This is awesome and surprisingly light, I can at the very least review this code and start thinking about reversing it in the other direction. Thanks so much.

Any other users, please still share your advice/experience if possible!

4

I would be thrilled if Roots wanted to take up maintenance of Lithify. I no longer work in WordPress so my time and capacity to troubleshoot in the environment is limited.

Another place to look is trellis-github-deployment which has a never-quite-worked “Eject” action which SHOULD (was originally intended to) create a portable, traditional-WordPress-friendly export of wp-content and the database.