Hosting Migration: Deliverables and Acceptance Checks

What should be delivered in the hosting migration service?

In the hosting migration service, it is not just copying the files to the new server; Database, domain connections, required application settings, and basic functional controls should also be covered. It should be clear what data will be moved, how the go live will be done, who will give the acceptance, and when the old service will be shut down. Moving e-mail accounts may be a task that should also be considered.

This article is a delivery-focused guide for businesses that want to migrate their existing website to another hosting environment. It does not say that every site will be migrated in the same way or in the same amount of time. The purpose is to explain what questions will be asked during the bid interview and how to recognize that the job has been completed. So you can consider the service not just as a file transfer, but as a controlled transfer of the running website.

The first deliverable is understanding the source environment

Before starting work, the technology, file structure and databases of the existing site should be determined. Site management and hosting management may be in the hands of different people. It should be learned who has domain name, DNS and application access. If this information is not ready, the inventory to be created during the initial review can be requested as a separate output. Incomplete access must be prevented from occurring on the day of transportation.

You do not need to send all passwords in a single file during the initial offer phase. What access the technical team needs and how this access will be granted should be planned together with the scope of work. If there are issues such as the management account being dependent on a personal employee, these should also be noted. Ensuring the company retains control over its assets is an essential part of the transfer process.

The list of data to be moved must be written

Files, databases and settings required for the application can be listed under separate headings. If there is more than one site in a panel, it should be stated which ones are included in the scope. Subdomains, test environments or legacy folders may also exist. Find out to what extent the provider bases its decision on moving all visible data versus just moving the active site.

The official shipping documentation for WordPress explains the consideration of components such as data and site address during environment changes; It also draws attention to backup preparation before the process. It should not be concluded from this that every site will be moved with the same file structure. The appropriate method should be selected according to the application used. The scope should be based on the actual structure of the site.

The suitability of the new environment should be examined before transfer.

The target hosting environment must meet the requirements of the application. The versions used, required components and external service connections are examined. A feature that works on the existing site is not automatically assumed to have the same conditions in the new environment. If there are issues that require an application developer, it should be determined in advance who will coordinate this.

Keep hosting migration and app development separate. An old plugin bug or existing software issue found during the migration may require additional work. Ask the provider to explain what compatibility checks it will perform and which fixes are out of service. In this way, the problems that existed before and the deficiencies created by the transportation can be separated more clearly.

Let the person responsible for domain name and DNS changes be determined

The domain name may be managed by another company and the hosting may be managed by another company. The authorized person who will make the DNS change should be included in the project plan. It should be determined which records will be changed and for what purpose; When moving the website, irrelevant e-mail or other service records should not be changed randomly. Having existing records in the initial inventory makes this control easier.

Changes made to DNS should not be expected to be seen by different users at the same time. The transition approach is prepared taking into account this behavior and current conditions. Rather than promising an exact deployment time, the technical team should explain what controls will verify the use of the new environment. Moving the domain name to another registrar is not automatically the same process as changing hosting.

Create a test list before going live

Opening the home page in the new environment is a basic control; But it may not be enough on its own. Important pages, images and internal links should be examined. If there is user login or content management, their operation is also checked. The acceptance list should be prepared according to what business the company uses the site for. The same number of tests may not be required in every project.

For example, while it is important for the contact form to work correctly on a service site, the cart or order steps may also be critical on a site that takes transactions. These are sample acceptance scenarios; it is not proof of actual customer success or a specific outcome. If the test produces a real order or e-mail, side effects should be checked and, if necessary, a safe test method should be determined.

Forms and email submission must be verified separately

The fact that the contact form displays a success message on the screen does not alone prove that the notification has reached the correct address. The registration, notification and error flow of the form should be examined. If sending from a server or an external service, it should be checked that the new environment is compatible with this connection. The party who knows the access method used by the application may be required to participate in the study.

Moving a website is different from moving mailboxes. User accounts, legacy messages, and device installations linked to your domain may require separate coverage. Ask what action is being taken in the offer instead of general statements such as “mail included”. If the postal service will also change mail migration work should also be planned. Thus, the transfer of the website and the management of company correspondence are not confused.

Addresses and directions must be protected

It is not mandatory to change web addresses when changing hosting. If existing domain names and page paths can be preserved, these should be included in the admission control. It is examined that known important pages respond correctly in the new environment. If there are old redirects or application server settings, their required counterparts should be evaluated. Having different server software in the new environment may require additional review.

It should not be said that changing hosting will automatically result in better search rankings. The technical goal is to protect the working content and the necessary access signals. If a domain name or address change is to be made, this should be planned separately. Instead of carrying out different projects at the same time in an uncertain manner, which changes were made and why should be written down.

Schedule updated data during migration

While the site migration copy is being prepared, new content, form registration or orders may continue to be created. It should be determined in which environment this data is created and how it will be handled in the final transfer. It should not be assumed that just by retrieving the first copy, all subsequent transactions of the active site are also migrated. If necessary, the appropriate working window is agreed with the application manager.

The business must disclose the times when changes may be made and the impact of the closure. The technical team should also specify the conditions to be considered and how to proceed with the unexpected outcome. Instead of promising zero interruption or zero data difference in any case, it is necessary to see the method and control steps suitable for the application. The acceptance decision should be made based on this plan.

Delivery report and closure of legacy service

The delivery report should include the sites moved, key changes made, checks completed, and any remaining open work. It should be stated how domain name and application access is delivered to the company official. A technical report should not just be a long list of transactions; It should also include a summary so that the customer can understand what is in store. This makes it easier to follow up on any problems that may arise later.

The closure of the old hosting must be confirmed separately. The service should not be terminated before the required data is received or the acceptance checks are completed. The scope, access and storage conditions of the copies to be kept are also agreed upon. Note that a temporary migration copy is not the same as an ongoing backup service. The expectation of regular backups for the new environment should also be explained.

What limits should there be on post-migration support?

After the project is completed, it should be determined how transportation-related deficiencies will be reported. Adding new content, changing the design or developing new features may be different tasks. The duration of the first term support and what it covers should be written in the proposal. In cases where the problem may be caused by the hosting, application or other service, the investigation method should be explained.

If you want ongoing application maintenance, specify this separately. For example, WordPress theme and plugin updates are different from just offering hosting space. Once the necessary maintenance and management plan is established, subsequent requests can be directed to the right team. In this way, it is not unclear who will handle which job after the move, and your company maintains control of its own system.

Submit your hosting migration request to İz Medya

The current site address, application used, approximate amount of data and migration expectation are useful for initial evaluation. Specify whether the email service will also change. You don't have to guess and fill in technical details you don't know; You can write them as topics to be verified in the initial review. Do not share passwords or sensitive customer data in the first form message.

İz Medya hosting serviceis prepared specifically for demand in its own cloud environment. If you have an application that requires a separate operating system or special configuration VPS server option We can also evaluate. Before the work begins, the data list, tests, migration method and cost are put in writing. This way, the delivery of the service you purchase is clearly defined beyond the file copy.

Frequently Asked Questions