Architecture studio: Divi site + portfolio CPT
Combined pattern we see often: AIRA for Divi marketing pages, parallel CPT migration for portfolio records, shared redirect map.
Marketing pages
0
Portfolio CPT posts
0
WXR + selective crawl
Manual estimate
0h
AIRA time
~2.5h
Blocks — no edit
0%
~29.5 hours saved vs manual estimate on this project
Tooling: £24.49 (31 credits)
The challenge
Portfolio projects lived as a custom post type with Divi-built singles. Marketing pages were standard Divi layouts. The agency had to move both without breaking /work/ archive URLs or losing project photography metadata.
Migration labour: manual vs AIRA
Anonymous production project — figures reported by the delivery team
Block accuracy after review
~22% of blocks still needed manual images (often SVGs)
- No edit 71%
- Minor edits 21%
- Major edits 8%
Approach
- 01
CPT registration on new theme
Rebuilt project post type, ACF fields for location, year, and gallery before any import.
- 02
AIRA for 31 pages
Crawled marketing and about pages. Portfolio singles crawled selectively — twelve flagship projects; remainder bulk-imported.
- 03
Archive template QA
Verified /work/ grid pulled CPT posts, not migrated Divi page duplicates.
- 04
SEO parity
Yoast meta migrated with bundles. Redirect map covered renamed project slugs from client rename pass.
“The portfolio was the scary part. Turns out the marketing pages were the time sink — once those were drafts, we could focus on /work/ properly.”
Agency project lead (anonymous)
Lessons
- lightbulbCPT migration is a separate workstream — pair with page crawl, do not skip it.
- lightbulbFlagship portfolio singles deserve manual review even when marketing pages bulk-import cleanly.
FAQ
Why not crawl all 48 portfolio posts?expand_more
Twelve hero projects needed block-perfect galleries; the rest imported via WXR into the new CPT template with ACF fields. Hybrid approaches are common on CPT-heavy sites.
Anonymised project — figures reported by delivery teams
Start free crawlarrow_forward