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

**URL:** https://discourse.roots.io/t/any-starting-tools-or-advice-for-a-bedrock-standard-wp-build-migration/30396
**Category:** radicle
**Created:** 2026-07-09T16:21:42Z
**Posts:** 3

## Post 1 by @jdinbound — 2026-07-09T16:21:42Z

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.

---

## Post 2 by @ben — 2026-07-09T16:33:54Z

This is a guide for Bedrock, not for Radicle, that uses [Lithify](https://github.com/MWDelaney/lithify):

> **[Converting WordPress Sites to Bedrock | Bedrock Docs](https://roots.io/bedrock/docs/converting-wordpress-sites-to-bedrock/)**
>
> Convert traditional WordPress sites to Bedrock using Lithify. Automatically updates database references and file paths for Bedrock's directory structure.

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.

---

## Post 3 by @jdinbound — 2026-07-09T16:45:45Z

_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!