Your website has a repository. It also has years of content, uploaded documents, form destinations, domain settings, and a handful of connections someone set up before the current team arrived.
A hosting move needs to account for all of that.
Before choosing a moving date, build a short picture of the working website. It will help your team and prospective host discuss the same project, including the pieces that are easy to overlook.
Make an inventory of the site you run
Begin with the software foundation: the Drupal version, modules, themes, dependencies, and custom functionality your site uses. Identify who understands that code and where development work happens.
Then account for the site’s database and uploaded files. Record where they live, who can access them, and how your team would obtain a current copy for a move.
Add connected services: email delivery, search, analytics, identity providers, payment or donation services, and anything else visitors or editors depend on. Your project may use only a few. Each still needs a place in the plan.
Agree on the supported move
Share the inventory with the host you’re evaluating. Ask which requirements its environment supports and how each part of the site would be transferred.
At Drupito, bringing your own codebase is a hosting starting point. Discuss database and file transfer, compatibility, and any assistance separately so everyone understands the steps required for your particular website.
Assign an owner to each step. If a developer needs to prepare the code, someone needs to transfer the files, and another person controls the domain, include all three in the schedule.
Test against a real visitor’s goal
A homepage that loads is a useful first check. The more revealing checks follow a complete task.
For a training site, that might mean finding a course and following the enrollment route. For a nonprofit, it might mean finding a program, downloading a document, and sending a question to the right team.
Check editorial tasks, too. Can the right people sign in, update content, upload files, and publish? Review connected services in an appropriate test setup, taking care that test actions do not trigger real customer transactions or duplicate notifications.
Write down the expected result for each critical journey so the team can judge whether the site is ready.
Decide how the final changeover will work
Content can keep changing while you prepare a move. Agree on how to capture the latest changes and whether there will be a short editing pause.
Name the person who will make the domain change, the person who will verify the live site, and the person who can decide what happens if a critical check fails. Establish a recovery approach with the people responsible for both environments.
Keep the previous arrangement available for the agreed verification period. Decide when it can be retired after the team has checked the live result.
Give the move a clear finish
After the changeover, confirm that visitors and editors can complete their important tasks. Check incoming requests and connected services. Update the team’s access and support records.
Your plan can fit on a page if the project is simple. What matters is accounting for the whole working site, with an owner for each handoff.
Considering Drupito for an existing project? Explore the hosting offer, then use your inventory to work through what your website needs for a move.