Website Import & Vetting

The full process for vetting, importing, and supporting WordPress websites migrated into Kaseya's WordPress Hosting environment.

For: Onboarding  |  MSS  |  Sales Teams  |  Web Development

Who uses this: Product Specialists, Onboarding, Marketing Support, Website Developers, and Website Support. Applies to all website import requests under Express and Pro packages. This is a fully managed service — the team owns everything from HubSpot intake through partner go-live approval.
Purpose & Scope

This guide covers the full process for vetting, importing, and supporting WordPress websites migrated into the WordPress Hosting environment under the MSP Success Digital Program.

Only WordPress and Duda websites are supported. Sites on Wix, Squarespace, Web Flow, HubSpot, or other platforms cannot be imported. Every site must be vetted and approved before import begins. WordPress Hosting is not activated until eligibility is confirmed.
How It Works — Step by Step

The full workflow from the partner's initial request through ongoing support. Each step shows who's responsible and what needs to happen.

StepOwnerActionDetails
1 Onboarding Complete Onboarding Assessment When a partner completes the onboarding assessment, they will choose their website intent. This information is logged in HubSpot, kicking off the workflow.
2 HubSpot Auto-assign task HubSpot automatically assigns a vetting task to Troy Bruinsma.
3 Troy Bruinsma Collect credentials Troy contacts the partner to get WordPress admin login and domain registrar access. All 6 required credentials must be provided before vetting starts.
4 Troy Bruinsma Submit vetting order Once all credentials are in, Troy submits the vetting order in AMP.
5 Dev Team Evaluate the site Dev team reviews the site against eligibility criteria. Takes 3 business days if credentials are correct and complete.
6a Troy Bruinsma Approved — Email partner Confirm WordPress Hosting + Website Support activation. Share go-live timeline. Remind partner: site does not go live until they give explicit approval.
6b Troy Bruinsma Rejected — Email partner Send rejection with the specific reason(s) and the right alternative path (see Section 5).
7 Website Support Complete import After product activation: migrate the site, connect the custom domain, and hold for partner go-live approval.
SLA Timeline

Quick reference for turnaround times at each stage.

PhaseSLANotes
Order Confirmation 3 business days from order receipt Confirmation email sent to MSP partner.
Website Vetting 3 business days from form receipt All 6 credentials must be provided. Missing info pauses the clock.
Import & Domain Connect 10 business days after approval + activation Products activated first, then import. Partner must approve go-live.
Required Credentials

All six items below must be in the fulfillment form before vetting can start. Missing anything? The clock pauses.

1
Domain registrar name
2
Domain registrar username
3
Domain registrar password
4
Current WordPress site URL
5
WordPress admin username
6
WordPress admin password
Delegate Access credentials are also accepted. If credentials are incomplete, the vetting clock stops until they're provided.
What Gets Rejected (and What to Offer Instead)

If a site hits any of these, it can't be imported. Always communicate the specific reason and the recommended alternative.

Disqualifying Condition Why It's Rejected Recommended Alternative
Not built on WordPress (or Duda)Only WordPress and Duda imports are supported.Duda: Accelerated Templated Website. Others: Templated, Express, or Tailored Build.
Fully custom-coded themeCustom themes can't be reliably managed or updated on the platform.New WordPress build with a supported theme framework.
Gutenberg/WP blocks only (no builder or theme)Block-only builds without a standard theme can't be managed post-import.New WordPress build with a supported builder.
Outdated or mixed-version pluginsInsecure or incompatible plugin versions create instability and risk.Clean up plugins and resubmit, or recommend a new build.
Heavy reliance on ACF / complex custom fieldsOverly complex ACF setups are reviewed case-by-case; poorly done ones get rejected.Case-by-case review. May require a rebuild.
Unapproved theme builderTheme builders outside the supported stack can't be maintained.Rebuild with a supported builder.
HTML/PHP theme pages or non-editable layoutsPages that bypass WP admin editing are unsupported.New build.
Too many plugins or user accountsCreates security risk and support overhead.New clean build.
WP admin not in EnglishThe team operates in English only.Switch WP admin to English and resubmit.
WordPress multisite networkMultisite imports are not supported.Create a standalone WP installation.
Relies on non-standard functionalityCustom APIs or proprietary server-side integrations are out of scope.Scope custom work separately or recommend rebuild.
Escalation & Exception Handling

After vetting is complete, Troy sends the partner one of the following:

Approved

  • Confirm activation of WordPress Hosting Premium + Website Support
  • Share the expected go-live date
  • Remind partner: site does not go live until they give explicit approval

Rejected

  • Send rejection email within the vetting SLA window
  • Include the specific reason(s) the site was rejected
  • Present the right alternative path (see Section 5 table)
  • Log the outcome in HubSpot