On this page4 sections

Every agency has that one client on WordPress with nine page builders and a plugin nobody dares to update. Here is the five-day plan we follow when we help an agency move one of them to Quillstack.

Day 1: model the content

Export the database and list every post type, custom field and shortcode that is actually used. On a typical 400-page site we find around 60 custom fields, and fewer than 20 are still filled in on pages from the last two years. Model those, not the rest.

Day 2 and 3: import

Run the importer against a staging copy:

npx @quillstack/cli import wordpress \
  --source https://staging.client.com/wp-json \
  --workspace client-acme \
  --map ./field-map.json

field-map.json maps WordPress fields to your new model. Anything the importer can’t map lands in a legacy field, so nothing is lost and you can clean it up later.

Day 4: rebuild the templates

The front end is the slowest part, so start it on day 1 in parallel. By day 4 it should read from Quillstack’s staging workspace.

Day 5: freeze, sync, switch

Morning

Tell editors to stop publishing at noon. Run the importer one more time with --since set to the first import, which only pulls pages changed since then.

Afternoon

Point DNS or the host’s rewrites at the new front end. Keep WordPress running read-only for 30 days in case someone needs an old revision.