Codex migrates WordPress sites with a reusable skill
John Curtis used Codex to move WordPress sites from WP Engine to SiteGround. A first-site migration followed by skill creation and a faster subsequent batch, including DNS changes, was reported by the poster, who logged in, granted permissions and tweaked the skill.
x.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Help migrate my WordPress sites from WP Engine to SiteGround using the accounts I provide. Ask for permissions when needed. After the initial migration, create a reusable skill for repeating the work, and identify unresolved issues before proceeding with further sites.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- @jcurtis
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The first site finished after 4 hours; building the skill took ~20 min with human tweaks; the next 7 sites moved in 30 minutes including DNS changes, reported by the poster. No calculated total time or savings is established.
- Human involvement
- Curtis logged into all required accounts, intervened to grant SFTP-related and other permissions, requested the reusable skill and tweaked it. A separate post-migration inspection is not described.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Curtis logged into the needed hosting accounts in the Codex browser and asked Codex to figure out the migration.
- Codex migrated the first site while Curtis intervened to grant SFTP-related and other permissions.
- Curtis asked Codex to create a reusable migration skill and contributed tweaks while it was built.
John Curtis had postponed moving WordPress sites away from WP Engine because the sites no longer needed that hosting service. Mixed WordPress versions and plugin activations made the move feel risky. An earlier attempt to migrate to SiteGround had hit a problem and been abandoned. This account concerns finishing that deferred maintenance, not building a new site.
Curtis logged into the required accounts through the Codex browser and asked Codex to work out the migration. The first site finished after 4 hours, reported by the poster. He intervened to grant SFTP-related permission and other permissions, so this was not an access-free or entirely hands-off process.
After that initial migration, Curtis asked Codex to create a reusable skill so the work could be repeated more confidently and in parallel. Building the skill took ~20 min, reported by the poster, with Curtis contributing tweaks. The next 7 sites moved in 30 minutes, including DNS changes through the Codex browser, reported by the poster.
The useful distinction is between the exploratory first migration and repeating the task with a skill built from that experience. Curtis supplied account access, handled permission requests and adjusted the reusable instructions; Codex carried out the migration work. The post does not provide a site-by-site validation record, describe rollback preparation or establish measured cost savings. Its timings are a self-reported account of this particular migration, not a general hosting-migration benchmark.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: X · @jcurtis
Frequently asked questions
What did Curtis do himself during the migration?
He logged into the needed accounts in the Codex browser, granted SFTP-related and other permissions, requested a reusable skill and helped tweak it.
How did the first migration compare with the later sites?
The first site took 4 hours. Building the reusable skill took ~20 min with human tweaks. The next 7 sites moved in 30 minutes including DNS changes, reported by the poster.
Does this account establish hosting savings or migration reliability?
No measured savings or reliability benchmark is established. The post describes a completed migration, reported by the poster, without a site-by-site validation record or rollback details.
More details
Remaining steps
- Codex used the repeatable workflow for the next sites, including DNS changes through the Codex browser, reported by the poster.
About this account
Codex worked out the migration through its browser, created a reusable skill on request and handled subsequent site moves and DNS changes, reported by the poster.
Full captured X post read via mirror. Outcomes are reported by the poster, not independently verified. Prompt: suggested editorial wording, not an original task prompt. Keep the first-site, skill-building and subsequent-batch timings distinct. Do not calculate a total or savings. No separate inspection, rollback procedure or reusable skill contents are supplied.
Credit: @jcurtis
Source published
Added to Agents In Use
Source checked
Tools and topics
Codex · Codex browser · WP Engine · SiteGround · SFTP
WordPress · Hosting migration · Reusable skills · DNS
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.