Claude Code migrates a HubSpot blog to WordPress
Wil Reynolds delegated a HubSpot-to-WordPress blog migration to Claude Code after preparing MCP access, plugins and permissions. A staging site and transferred forms and tracking were reported by the poster; staging likeness was not independently verified.
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 HubSpot blog to a WordPress staging site using the connected MCPs. Identify required permissions and dependencies before starting. Include forms and tracking in the migration scope, and summarize completed work and anything unresolved for my review.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- @wilreynolds
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- A HubSpot blog migrated to a WordPress staging site after 6 hours of autonomous work, with forms and tracking moved as embeds, reported by the poster. The completion email appeared in drafts; visual likeness was not independently verified.
- Human involvement
- Reynolds selected the destination, researched documentation, connected MCPs and prepared permissions, plugins and Python. He later showed people the staging site; no formal audit or production cutover is 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
- Reynolds used AI to compare blog-host MCP options and research HubSpot and WordPress documentation.
- With HubSpot and WordPress MCPs connected, Reynolds prepared permissions, installed plugins and set up Python before leaving his desk.
- Claude Code continued the blog migration unattended and identified forms and tracking to transfer as embeds, reported by the poster.
Wil Reynolds used Claude Code to move a HubSpot blog to WordPress. Before delegating the migration, he used AI to compare blog-host MCP options and chose WordPress for his needs. He also started research into documentation for both platforms. The account describes preparation followed by an unattended migration, rather than a request handed to an agent without setup.
HubSpot and WordPress MCP connections were already available. Reynolds used a business account for the new WordPress site to obtain full MCP access. Before leaving his desk, he worked through permissions, installed plugins and set up Python. He then gave Claude Code a window in which to continue without him.
The migration ran for 6 hours, reported by the poster. Reynolds says a completion email appeared in his drafts, not that a delivered notification was independently confirmed. Moving forms and tracking as embeds was also reported by the poster, who credits the agent with recognizing that requirement.
Reynolds describes showing people the staging site and says they could not distinguish it from the original apart from an accessibility icon. That likeness is reported by the poster and has not been independently verified here. The account does not establish a production cutover or a formal migration audit. His later image-insertion prompt concerns editing a post, not the migration, so the suggested prompt below is an editorial addition.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: X · @wilreynolds
Frequently asked questions
What did Reynolds prepare before leaving Claude Code to work?
He had HubSpot and WordPress MCPs connected, used a WordPress business account for full MCP access, and worked through permissions, plugin installation and Python setup.
Did the source confirm a live production migration?
No. Reynolds describes a staging site and says people could not distinguish it from the original apart from an accessibility icon. That likeness is reported by the poster, not independently verified.
Is the suggested migration prompt quoted from Reynolds?
No. His shared prompt concerns inserting an image into a post after the migration. The migration prompt here is suggested editorial wording, not his original request.
More details
Remaining steps
- A completion email appeared in Reynolds’s drafts; he later showed people the staging site and described its likeness to the original.
About this account
Claude Code continued the blog migration without Reynolds at his desk and identified forms and tracking to move as embeds, 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. Completion email appeared in drafts. Staging likeness is reported, not independently verified; production cutover is not established. The shared image-editing prompt is unrelated to the migration.
Credit: @wilreynolds
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · HubSpot MCP · WordPress MCP · WordPress plugins · Python
Blog migration · WordPress · HubSpot · MCP
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.