wiki/knowledge/wordpress/sbs-wordpress-migration.md Layer 2 article 909 words Updated: 2026-04-05
↓ MD ↓ PDF
wordpress migration hosting dns sbswi hibu siteground redirects

SBS WordPress Migration & Hosting Plan

Overview

SBSWI's current website is hosted on Hibu and is not built on WordPress — it uses a proprietary platform. The migration plan moves the site to a fresh WordPress installation on Asymmetric's hosting infrastructure, with the domain registration remaining at SiteGround. DNS management will transfer to Asymmetric at cutover.

Because the current site cannot be cloned into WordPress, the build is a ground-up rebuild using existing content as reference material, not a platform migration.

See also: [1] | [2]


Platform Stack (Current → Future)

Layer Current Future
CMS / Builder Hibu (proprietary) WordPress
Hosting Hibu Asymmetric
Domain Registrar SiteGround SiteGround (retained)
DNS Management SiteGround / Hibu Asymmetric (post-cutover)

Migration Approach

Why a Rebuild, Not a Clone

The existing Hibu site is not WordPress-based. There is no export or theme to pull into a new environment. The migration strategy is:

  1. Use the current site as a content reference — copy text, gather assets, inventory pages.
  2. Build the new site from scratch on a staging environment on Asymmetric hosting.
  3. Complete QA on staging before any DNS changes.
  4. Cut over DNS at launch, pointing the domain from SiteGround to Asymmetric servers.

Hibu Contract — 30-Day Notice Requirement

Hibu requires 30 days written notice to cancel hosting. Key considerations:


Domain & DNS Transition

Domain Retention at SiteGround

The domain (sbswi.com) stays registered at SiteGround. No registrar transfer is needed. At launch, the DNS nameservers or A/CNAME records at SiteGround will be updated to point to Asymmetric's hosting.

Access Requirements

DNS Deliverability Issues (CenterPoint Connect)

SBSWI uses CenterPoint Connect for proposals and service communications. There are known email deliverability issues tied to missing or misconfigured DNS records. At DNS cutover, Asymmetric will implement:

Asymmetric should gather the specific DNS record values from CenterPoint Connect documentation before cutover and prepare a deliverability plan in advance.


URL Preservation & Redirect Strategy

Why This Matters

SBSWI has QR codes deployed in the field (on materials, signage, etc.) that point to specific URLs on the current site. If those URLs change or break at launch, the QR codes become dead links.

Requirements

Brandon/SBSWI team should provide a list of any QR code URLs currently in active use in the field.


Staging & Launch Sequence

  1. Build new WordPress site on Asymmetric staging environment.
  2. QA — cross-browser, mobile, form routing, redirect testing, QR endpoint verification.
  3. DNS prep — finalize SPF/DKIM/DMARC/CNAME values; prepare DNS change instructions.
  4. Hibu notice — submit 30-day cancellation notice timed to launch date.
  5. Cutover — update DNS at SiteGround to point to Asymmetric; monitor propagation.
  6. Post-launch — confirm email deliverability, verify all redirects, decommission Hibu.

Access Checklist (Asymmetric to Send SBSWI)

Asymmetric (Sebastian/Melissa) to send a credentials request checklist to Brandon by Nov 22, covering:


Key Decisions Made


Open Items

Item Owner Due
Send credentials request checklist to SBSWI Asymmetric (Sebastian/Melissa) Nov 22
Provide Hibu portal access Brandon (SBSWI) Dec 1
Provide SiteGround login (via Megan) Brandon (SBSWI) Dec 1
Gather CenterPoint Connect DNS record values Asymmetric Pre-cutover
Prepare DNS/email deliverability plan Asymmetric Pre-cutover
Inventory QR code URLs in active field use SBSWI (Brandon) Dec 8
Decide Hibu notice timing Brandon (SBSWI) ~Jan 10