App Composer for WordPress and agency work.
All roles and jobsChoose by the job you need done
Prove one content move before a rebuild.
Try a portable content model and an owner-editable page. Check the content, media and ordinary editing your client actually needs before choosing a destination.
What works now, and what needs your setup
The migration lab has a small documented WordPress import; it does not establish Elementor, ACF, WooCommerce or whole-site parity. Keep WordPress when a required plugin, workflow or recovery path has no verified replacement.
Working as an agent? Choose a versioned role pack with inputs, evidence, stop rules and a runnable brief.
Device support not checked yet
The build story shows an authored content project and a fictional postcard moving through pending, approval, featuring and source removal.
Actual capture · 2026-10-18 · guestbook.loftwah.comKeep what already works.
Keep the existing site, URLs and client choices until representative editing, media and recovery checks pass.
Start here: Write one acceptance brief for a content type and its existing editor task.
Read the migration observationsFrom this example to your own project
List the behaviour to preserve
Record URLs, content types, media, forms, editor tasks and the plugins that supply them. Keep the current site as the reference.
Try one representative model
Use a maintained model and its real form before authorising an isolated import of public or fictional content.
Review exact plugin evidence
Inspect the curated release, permissions and unknowns. Plugin installation needs a separately qualified native target.
Role names are starting points. Choose another job, browse all apps or return to App Composer.