1. Start with the site you actually need to protect
A hosting decision should begin with an inventory rather than a generic promise of speed. Identify the website, domains, subdomains, databases, forms, media libraries, redirects, SSL certificates, DNS records and any services that depend on them. Separate public website functions from administrative access and from third-party services. If your firm serves clients in Hopkins and elsewhere in Hennepin County, document which pages and intake paths are intended for each service area without treating the city’s population as a forecast of demand. Bosseo’s public page describes dedicated server resources, managed security and SSL, daily backups, 24/7 monitoring and an end-to-end migration service. Those capabilities are relevant only after you confirm that they match your site’s architecture and operating requirements.
Recommended approach
Ask for a written current-state inventory and a proposed target-state scope. Require clear ownership for the domain, DNS, website files, database, certificates, administrator accounts and recovery decisions. Do not approve a move until the inventory identifies what is included, what remains with another provider and who can authorize changes.
