Stop losing margin on content migration
AIRA crawls any client site, maps every section into your ACF block library, and imports as drafts — so rebuilds ship on time and editors get native Gutenberg, not leftover shortcodes.
1 credit = 1 page · Crawl and preview free · Pay when you commit
The rebuild problem agencies know too well
You've standardised on ACF blocks. The client site wasn't built that way. The gap between design sign-off and launch is where projects die.
Rebuilds overrun on content
Design and dev are scoped. Migration isn't — until a 40-page Elementor site eats two days of copy-paste and broken images.
Hard to quote accurately
Every builder stores content differently. Without a fixed unit cost per page, migration either blows the margin or gets under-scoped.
Editors inherit a mess
Handing over a site built from someone else's shortcodes means support tickets on day one. Native ACF blocks fix that — if you can get the content in.
SEO risk on launch
Redirects, meta, internal links — one missed URL and the client's rankings cliff. Migration QA can't be an afterthought.
How agencies use AIRA on client rebuilds
Export your ACF block library
Register blocks on the new build, export field groups as JSON. AIRA learns every block, field key and repeater — your portfolio standard, not per-client guesswork.
Crawl the old site (free)
Paste the client URL. AIRA discovers the sitemap, crawls each page, and classifies sections into your blocks with confidence scores. Filter paths so you only migrate what matters.
Review, commit, import drafts
Fix low-confidence blocks in the review screen. Commit the run (1 credit = 1 page), import via the ACF Migrate plugin as drafts — media sideloaded, links rewritten, SEO carried over.
Quote migration in credits, not guesswork
Crawl the sitemap first for an exact page count, or use these benchmarks when scoping before discovery. Extra credit packs never expire — useful when projects cluster.
Migration playbooks by source
In-depth guides for the builders and platforms your clients actually arrive on.
Built for studios running multiple rebuilds
Shared credits, team seats, and client workspaces — so migration isn't tied to one developer's login.
- check_circle750 credits/month on the Agency plan
- check_circleTeam seats and shared credit pool
- check_circleClient workspaces and roles
- check_circleWhole-site sitemap crawling
- check_circleRedirect map export (old → new)
- check_circleDedicated onboarding and support
Questions agencies ask
Is AIRA only for WordPress-to-WordPress migrations?
No. AIRA crawls any public URL — WordPress page builders, Webflow, static marketing sites — and maps rendered sections into your ACF blocks. The destination is always your WordPress build with a registered ACF block library.
How do agencies quote migration with AIRA?
Count the pages you're migrating (or crawl first to get an exact number). 1 credit = 1 page in the committed bundle. A 50-page rebuild is 50 credits — predictable enough to bake into your fixed quote or line-item it separately.
Does AIRA replace our developers?
It replaces the copy-paste grunt work — not the theme, block library, WooCommerce templates, forms, or launch QA. Your team still builds the new site; AIRA gets content into the right ACF fields so review and publish is hours, not days.
What do we need on the client's new WordPress site?
WordPress 6.4+, ACF Pro with your blocks registered, and the free ACF Migrate importer plugin. AIRA never writes to the old site — it only reads the public front-end.
Can we try it before pitching a client project?
Yes. Every account gets 10 free credits on signup. Crawling and classifying are free — you only spend credits when you commit and download the import bundle.
Run your next rebuild migration on AIRA
Crawl a client site free. See the block mapping before you spend a credit.
Open AIRA — 10 free credits