1. Start with the site you actually need to protect
A hosting decision should begin with an inventory, not a server label. List the public website, staging or development environments, forms, document downloads, analytics tools and any third-party services that must continue working after a move. Then identify who controls the domain, DNS, website administrator account and current hosting account. Bosseo describes migration support that can include files, databases, DNS, SSL and email records. Those items should appear in a written migration scope rather than being left to assumption. Olivette’s relationship to St. Louis County is relevant when you define the firm’s public service area and test location-specific pages, but it does not determine the technical configuration. Your site structure and administrative requirements do.
Recommended approach
Ask Bosseo to map the present environment before recommending a move. Require a list of included assets, required access, exclusions and the person responsible for approving the cutover.
