Seamless WordPress Migration Strategy

Overview

Seamless Building Systems' current website is hosted on a proprietary platform managed by Haibu — not WordPress. This means the site cannot be directly migrated or imported; AAG must perform a full rebuild on WordPress, then execute a clean cutover once the new site is ready.

This article documents the migration constraints, risks, and planned approach discussed during the ^[1].

Platform Constraint

Because Haibu uses a proprietary CMS, standard WordPress migration tools (XML import, plugin-based scrapers, etc.) cannot be used to lift content automatically. All pages — including 42 case studies, service pages, and blog posts — must be manually reconstructed or copy-pasted into the new WordPress environment.

Key Risk: Downtime Gap

The primary risk is a website blackout if Haibu service is cancelled before the new WordPress site is live and pointed at the domain.

"You wouldn't have a website for a little bit." — Melissa Cusumano

Brandon confirmed Haibu is month-to-month and requires a 30-day cancellation notice. Cancelling prematurely — even with notice — could result in the existing site going dark before the WordPress replacement is ready.

Mitigation: Do not notify Haibu until the new WordPress site is fully built, reviewed, and ready for DNS cutover.

Recommended Approach

1. Build in parallel — AAG constructs the full WordPress site in a staging environment while the Haibu site remains live and operational.
2. Content migration — Manually port all pages, case studies, and blog content. Brandon to prioritize top 20 case studies; remaining 22 can follow.
3. DNS cutover — Once the WordPress site passes QA, update DNS to point the domain to the new host. Haibu site remains on standby during propagation.
4. Cancel Haibu — Only after successful cutover and confirmed uptime on WordPress. Give 30-day notice at that point.

AAG committed to delivering a migration plan recommendation by end of week (week of 2025-12-08).

Content Scope

The site has more pages than initially scoped. Key content requiring migration:

• 5 service pages (Commercial Roofing, Roof Restoration, Asphalt Shingles, Single-Ply/TPO, Repairs)
• 42 case studies — all to be retained for SEO value; top 20 flagged for prominent placement
• Blog posts
• Homepage (full redesign; not a direct port)
• Contact / estimate form

Each service page requires a minimum of 1,000 words for SEO. Brandon will supply updated content via email; AAG will organize into a shared Google Doc.

Hosting & Access

SiteGround is the current hosting provider. Credentials were partially provided but confirmed non-functional as of the meeting date. Resolution path:

1. Sebastian audits all provided logins and reports what is missing or broken.
2. Brandon contacts Megan (virtual assistant) for correct SiteGround credentials.
3. AAG gains hosting access needed to configure the new WordPress environment.

See also: ^[2] for full account access status.

Open Questions

• Will AAG host the new WordPress site on SiteGround, or migrate to a different host?
• Does Haibu retain any rights to content or assets on their platform after cancellation?
• Can Haibu provide an export of any content (even partial) to reduce manual rebuild effort?

Action Items

Related

• ^[3]
• ^[4]
• ^[5]