How to Prepare Website Files and Databases for Migration

How to Prepare Website Files and Databases for Migration

Moving a website to a new hosting provider can improve its reliability, performance or support experience, but a migration should not begin with copying files at random. Website files and databases work together, and missing one important component can lead to broken pages, lost content, failed logins or an unavailable website.

For a Nigerian small business, entrepreneur or organisation, careful preparation is especially important when the website supports customer enquiries, online sales, business email or professional credibility. The goal is not simply to move data. It is to move the website with its content, settings, domain connections and essential access under your control.

Understand what needs to move

A typical website migration may involve several separate assets:

  • Website files: These include application files, themes, plugins, images, documents, scripts and configuration files.
  • Database: A database stores changing content such as pages, posts, product information, user accounts, comments and website settings.
  • Domain: The domain name directs visitors to the website, but it is separate from the hosting account.
  • Email: Domain-based addresses such as [email protected] may use different mail settings from the website.
  • DNS records: These tell browsers and email services where to find the website and mailboxes.
  • SSL configuration: HTTPS settings need to be available on the new hosting environment.

Not every migration involves all these items. For example, you may move website hosting while leaving email with its existing provider. Decide this before changing DNS records, because an incorrect change can interrupt business email even when the website migration itself is successful.

Confirm ownership and access first

Before downloading anything, make a list of the accounts involved. You should know who controls the domain registrar account, current hosting account, website administration account, database access and email service.

Business owners should retain access to these essential digital assets rather than relying only on a former developer, employee or third party. Confirm that the domain registration details and recovery email are accurate. Check the domain’s renewal status and ensure that any transfer or security restrictions are understood before migration.

Also record the current hosting details, including:

  • Hosting control panel login
  • File transfer access, such as SFTP or another available method
  • Database name, username and password
  • PHP or application version, if relevant
  • Current DNS records
  • WordPress administrator access, if the site uses WordPress

Do not publish passwords in a document shared widely with a team. Store credentials securely and change temporary passwords after the migration is complete.

Create a complete backup

A backup should be created before making changes to the existing website. Ideally, keep more than one copy and store at least one copy separately from the current hosting account. A backup that exists only on the server being migrated may be lost if that account becomes inaccessible.

For a database-driven site, a complete backup normally includes both the website files and a database export. Downloading only the visible images or public pages is not enough. You may also need configuration files, hidden files and folders used by the application.

Label the backup clearly with the website name and date. Then check that the files can be opened and that the database export is not empty or unusually small. A backup is more useful when you know what it contains and how it would be restored.

For WordPress websites

A WordPress backup should generally include the WordPress files, the wp-content folder and the database. The wp-content folder contains themes, plugins and uploaded media, while the database contains posts, pages, settings and other site information.

Review the plugins and themes before migration. Remove unused extensions where appropriate, update carefully, and make a note of any plugin that handles caching, security, redirects, backups or contact forms. These can affect the way the website behaves on a new server.

Export and prepare the database

The database export is often created through a hosting control panel or a database management tool. The exact process depends on the hosting environment, but the important outcome is a usable export containing the website’s tables and data.

Before exporting, consider the following:

  • Check that the correct database is selected, especially if several websites share one hosting account.
  • Record the database name, username and password used by the website configuration.
  • Allow the export to include the tables required by the application.
  • Use a suitable export format provided by the database tool.
  • Keep the original database unchanged until the new copy has been tested.

Large databases may need special handling. An export can time out when performed through a browser-based tool, or a large import may exceed limits on the new hosting account. In that situation, ask the new host about supported import methods rather than repeatedly attempting an incomplete transfer.

Check configuration files carefully

Website configuration files often contain the connection details that link the files to the database. They may also contain security keys, caching rules, directory settings or application-specific values.

Do not edit these files without keeping an original copy. When the website is moved, database credentials, file paths or server-specific settings may need to change. A small typing error can produce a database connection error or a blank page.

Configuration files can also contain sensitive information. Transfer them securely and avoid sending them through unsecured public channels. If credentials were exposed during the process, replace them after the migration.

Record DNS and email settings

Before changing the domain’s DNS, save a copy of the existing records. Common records include those for the website, email delivery, subdomains and verification services.

This step is essential when the same domain is used for business email. If you move the website but accidentally remove or replace mail records, messages may stop arriving. The safest approach is to change only the records required for the website and leave email-related records unchanged unless email is also being migrated.

Tell colleagues or service providers about the planned change if they manage email, payment tools, analytics or other services connected to the domain. Keep a record of which service controls each part of the setup.

Prepare the new hosting account

Before uploading the website, confirm that the new hosting environment can support it. Consider the application requirements, storage needs, database type, email requirements, SSL support and expected visitor traffic. A small brochure website may need a different arrangement from a busy online store or a website with several mailboxes.

For WordPress, confirm that the new environment supports the required WordPress version and the versions used by the website’s themes and plugins. If the site needs managed WordPress support, clarify which maintenance responsibilities are included and which remain with the website owner.

Create the required database and user on the new hosting account, then apply the appropriate permissions. Upload the files to the correct web directory and import the database using the method supported by the new host.

Test before directing visitors to the new server

Do not wait until the DNS change to discover that the website is broken. Use a temporary preview address or another testing method provided by the hosting provider. The exact preview method varies, but the principle is the same: test the new copy while the existing website remains available.

Check important functions rather than only opening the homepage:

  • Open several pages and posts.
  • Test navigation, images, downloads and internal links.
  • Log in to the administration area.
  • Submit contact forms and confirm where messages are delivered.
  • Test shopping carts, payments or bookings if applicable.
  • Check mobile layouts, since many visitors in Nigeria and West Africa access websites primarily through mobile devices.
  • Confirm that HTTPS works and that browsers do not show security warnings.
  • Review redirects and important error pages.

For a business website, submit a real but low-risk test enquiry and confirm that the recipient receives it. If the website uses domain-based email, test both sending and receiving without altering the existing mail settings unnecessarily.

Change DNS and monitor the migration

Once the new website has been tested, update the relevant DNS record or nameservers according to the migration plan. DNS changes may not appear everywhere immediately because different networks and devices can temporarily use cached information.

Keep the old hosting account active until the new website is working consistently and you have confirmed that important data is present. Monitor the website, forms, logins and email during this period. Do not cancel the old service simply because the domain begins displaying the new server.

Keep a migration record

Save the final backup, DNS record list, access details, test results and date of the change in a secure location. Note any settings that were changed and who is responsible for future renewals, backups and updates.

A successful migration is more than a website appearing at a new address. It means the files and database are complete, the domain remains under the business’s control, email continues working, HTTPS is active and the owner has a reliable recovery path.

The practical takeaway: prepare first, back up both files and database, protect email settings, test before changing DNS and keep control of your domain and hosting accounts. If the technical steps feel unclear, a hosting provider such as Sonhosting can handle the complicated parts while explaining what is being moved and why.

How to Transfer a Domain Without Losing Your Website

How to Transfer a Domain Without Losing Your Website

Moving a domain to a new registrar or hosting provider can improve support, simplify management or bring your website and domain into one account. But a domain transfer is not the same as moving a website. If the steps are handled in the wrong order, your website may become unavailable, business email may stop working, or you may lose access to important services.

The safest approach is to treat the process as two separate tasks: transferring control of the domain registration and, if necessary, moving the website hosting. Understanding the difference helps Nigerian businesses, entrepreneurs and organisations protect their online presence while changing providers.

Domain transfer and website migration are different

Your domain is the address people use to reach you, such as yourbusiness.com. Hosting is the server space where your website files, database and applications are stored. Business email may use the domain but can be hosted separately again.

Transferring a domain changes the company responsible for managing the registration. It does not automatically copy your website files, WordPress installation, database, email messages or backups to the new provider.

For example, if your website is hosted with Provider A and you transfer the domain to Provider B, the website can continue working from Provider A. The domain’s DNS settings must still point visitors to the correct hosting server. If you also want to move the website, that should be planned as a separate migration.

Before starting: identify what could be affected

Make a simple inventory of the services connected to your domain. This prevents surprises during the transfer and helps you confirm that every important service is restored afterwards.

  • Website: Identify where the website is hosted and whether it uses WordPress or another platform.
  • Email: Record where your business email is hosted. Check whether messages, contacts and calendars need to be copied.
  • DNS: Note the current nameservers and important records, including A, CNAME, MX, TXT and any verification records.
  • Security services: Check whether your domain uses an SSL certificate, content delivery service, firewall or email security provider.
  • Account access: Confirm that you can access the current registrar account, the administrative email address and the account where the domain will be transferred.

If a developer, former employee or third party registered the domain, resolve ownership and access issues before beginning. A business should retain control of its domain account and use accurate contact information rather than relying on one person’s private email address.

Back up the website and record your settings

A domain transfer normally does not delete website content, but a backup is still an essential precaution. Save a recent copy of the website files and database, especially if the domain transfer will happen at the same time as a hosting migration.

For a WordPress website, the backup should include the database, themes, plugins, media uploads and configuration information. Keep a copy somewhere separate from the current hosting account. Also confirm that you know how to restore the backup instead of assuming that a backup exists merely because a hosting panel shows a backup option.

Export or document the DNS zone before changing providers. You may need records for:

  • The website’s IP address or hosting destination
  • Business email delivery through MX records
  • Google, Microsoft or other service verification
  • Sender authentication, such as SPF, DKIM and DMARC records
  • Subdomains used for applications, payments, forms or customer portals

Missing one of these records may not take down the main website, but it can break email delivery or a connected service.

Prepare the domain for transfer

Most domain transfers require several conditions to be met. The exact process depends on the domain extension and registrar, so check the instructions for your specific domain. Common preparation steps include:

  1. Confirm the domain is active. Do not wait until the domain is close to expiring. Renewal and transfer processes can take time, and an expired domain may have additional restrictions.
  2. Unlock the domain. Many registrars apply a transfer lock to prevent unauthorised movement. The lock usually needs to be removed before a transfer can start.
  3. Request the transfer authorisation code. This may be called an EPP code, auth code or transfer code. Treat it like a password and share it only through the new registrar’s secure transfer process.
  4. Check the registrant and administrative email. Transfer notifications may be sent to an address associated with the domain. Make sure it is accessible and current.
  5. Review transfer restrictions. Some domains may have a temporary restriction after a new registration, recent transfer or recent change to registration details. If a transfer is blocked, the current registrar should explain the reason.

Do not cancel your existing hosting or registrar account at this stage. Keep the old service active until the domain, website and email have been tested successfully.

Start the transfer with the new provider

Enter the domain and authorisation code in the new registrar’s transfer area. Carefully check the spelling of the domain before submitting the request. A small spelling error can lead to transferring the wrong domain or starting an unsuccessful request.

Watch for approval messages sent to the domain’s registered contact. Some transfers complete after the required approval steps; others may take longer while the registrars process the request. Avoid making unrelated DNS changes while the transfer is pending unless you have a clear reason and a backup of the original settings.

A transfer can change who manages the domain registration without changing where the DNS points. That is why the website can often remain online during the process, provided the nameservers and DNS records are preserved.

If you are moving the website too

When changing both domain registrar and hosting provider, use a staged workflow rather than switching everything at once.

  1. Set up the new hosting account.
  2. Copy the website files and database to the new server.
  3. Test the website using the temporary address or another safe testing method.
  4. Set up email accounts and confirm the required DNS records.
  5. Install or activate HTTPS on the new hosting environment.
  6. Reduce the DNS time-to-live in advance if your provider recommends it, so planned DNS changes can be recognised more quickly.
  7. Change the relevant DNS records or nameservers when the new website is ready.
  8. Test the website, forms, login areas and email before cancelling the old service.

Do not make a DNS change until the new hosting account is ready to serve the website. Pointing the domain to an empty or incomplete account can create downtime even though the domain transfer itself was successful.

Check the website, email and security after transfer

Once the transfer or DNS change is complete, test from a phone and computer. Mobile testing matters because many customers in Nigeria and West Africa discover businesses through mobile devices.

  • Open the main website and several important pages.
  • Submit contact, enquiry or order forms.
  • Check images, links, menus and WordPress login access.
  • Confirm that the website loads with HTTPS and does not show certificate warnings.
  • Send test emails to and from the business address.
  • Check whether messages are delivered to major recipient providers.
  • Test subdomains, payment pages and other connected services.
  • Confirm that the domain renewal date and payment method are visible in the new account.

Some visitors may continue reaching the old destination temporarily because DNS information is cached. Keep the old hosting account available during this transition and monitor both services where possible.

Common problems and how to avoid them

The website disappears after the transfer: The nameservers or A record may no longer point to the correct hosting account. Restore the documented DNS settings and confirm the new server is configured for the domain.

Email stops working: The MX records may be missing or pointing to the wrong email provider. Recreate the required MX, SPF, DKIM and DMARC records based on the email provider’s instructions.

The transfer cannot start: The domain may be locked, the authorisation code may be incorrect, the contact email may be inaccessible, or a transfer restriction may apply. Contact the current registrar before repeatedly submitting requests.

The business loses access: This often happens when account details belong to a former employee, web designer or agency. Update ownership, recovery email addresses and passwords, and store the information securely.

A safer way to manage future changes

Keep a private record of your domain registrar, renewal date, DNS provider, hosting account and email provider. Use strong, unique passwords and enable available account security features. Set renewal reminders well before expiry rather than relying on memory.

For a business that does not want to manage server settings, a managed hosting provider can handle the technical migration while explaining what is changing. The important point is not to surrender ownership: support teams can manage the work while the business retains access to its domain and essential accounts.

A successful domain transfer is largely a preparation exercise. Back up the website, record DNS and email settings, keep the old service active, transfer the domain separately from the website when possible, and test every customer-facing service afterwards. With that workflow, you can change providers without sacrificing the website, email and trust your business has built online.

How to Move Your Website to a New Hosting Provider Without Disruption

How to Move Your Website to a New Hosting Provider Without Disruption

Moving your website to a new hosting provider can solve problems such as slow loading, unreliable support, limited resources or difficult account management. However, a migration involves more than copying website files. Your database, email accounts, domain settings, SSL certificate, backups and WordPress configuration may all be connected.

A careful migration can usually be completed with little or no noticeable disruption. The key is to prepare before cancelling the old hosting account, keep control of your domain and test the new website before directing visitors to it.

What a website migration usually involves

When people say they want to “move their website”, they may mean several different things:

  • Website files: Images, themes, plugins, HTML, scripts and other files stored on the server.
  • Database: Content, settings, user accounts, orders and other information used by systems such as WordPress.
  • Domain: The web address visitors type into their browsers. The domain and hosting are separate services.
  • Email: Mailboxes and messages associated with your domain, such as [email protected].
  • DNS records: Instructions that connect your domain to your website, email provider and other services.
  • SSL certificate: The security configuration that enables HTTPS.

Not every migration requires moving all these services to the same provider. For example, you may move your website hosting while keeping email with a separate provider. Decide what is changing before you begin.

Before you start: create a migration plan

Make a list of everything currently connected to your website. Include the domain registrar, hosting account, email provider, WordPress administrator account, payment or booking integrations, analytics tools and any third-party services.

Also record who controls each account. A business should not depend on a former developer, employee or unknown third party to access its domain or website. Confirm that your organisation has the correct login details, recovery email address and ownership information.

For a small Nigerian business, this preparation is particularly useful when a website was created by different people over time. It can prevent a domain renewal or email problem from becoming an emergency during the migration.

Check the new hosting plan

Choose a plan that matches your actual needs rather than automatically selecting the most expensive option. Consider:

  • The website’s storage and database requirements.
  • Expected traffic and future growth.
  • Whether you need WordPress support or prefer to manage the site yourself.
  • How many business email addresses and mailboxes are required.
  • Backup, security and SSL requirements.
  • The level of technical support you need.

If you run a simple company website, a modest hosting plan may be enough. A busy online store, membership website or application may need more resources and specialist support. The right choice depends on the website, not on a generic hosting label.

Step 1: Back up the existing website

Do not begin by deleting anything from the old server. First create a complete backup of the website files and database. If email is also being moved, plan a separate backup or export of important messages.

For WordPress, a useful backup should include the WordPress files, uploaded media, themes, plugins and database. A copy stored only on the old hosting account is not enough. Download a copy to a secure location so you have a fallback if the migration fails.

Check that the backup is usable. A backup that cannot be restored is not a reliable recovery plan. If you are uncertain how to back up or restore the website, managed WordPress support or assistance from your hosting provider can reduce the risk.

Step 2: Prepare the new hosting account

Set up the new hosting account before changing the domain’s DNS settings. Most providers give you temporary access through a preview address, server address or staging arrangement.

Install the required software and create the necessary database. If you are moving WordPress, check that the new environment supports your WordPress version, theme and plugins. Upload the website files and import the database according to the provider’s instructions.

Some migration tools can copy a WordPress website automatically. They may save time, but they still require testing. Large media libraries, unusual server settings, security plugins or custom code can cause problems that an automated tool does not identify clearly.

Step 3: Test the website before changing DNS

Test the new copy using its temporary address or another private method. Review the pages that matter most to customers:

  • Homepage, service pages and contact information.
  • Contact forms and enquiry notifications.
  • Images, downloads and embedded videos.
  • WordPress login and administrator functions.
  • Shopping cart, checkout or booking features, if applicable.
  • Mobile display and page loading behaviour.
  • Links between important pages.

Check that your Nigerian customers can easily find the correct phone, email, location and enquiry options. A migration is a good opportunity to notice outdated contact details or broken forms, but avoid making unnecessary website changes at the same time. Keeping the migration focused makes troubleshooting easier.

Step 4: Plan the DNS change carefully

DNS records tell the internet where to find your website and email. To point the domain to the new hosting provider, you may need to change nameservers or update specific records, such as the A record.

Do not change DNS until the new website is ready. Before making the change, write down the current DNS records, especially email-related records. These may include records used for mail delivery, verification and email security. Removing them accidentally can interrupt business email even when the website itself works correctly.

DNS changes can take time to appear across different networks. During this period, some visitors may reach the old server while others reach the new one. Keep both hosting accounts active and avoid making different content changes on each version.

Step 5: Move or reconnect business email

Email deserves separate attention because it is easy to overlook during a website migration. Decide whether email will remain where it is or move to the new provider.

If email is staying with the current provider, preserve the relevant DNS records and confirm that mailboxes continue to work. If email is moving, create the mailboxes first, migrate important messages where possible and update the DNS records only after the new service is ready.

Test sending and receiving messages from different accounts. Also check phones, computers and email applications used by staff. A website can appear fully operational while customer enquiries are silently failing because email records were changed incorrectly.

Step 6: Confirm HTTPS and website security

After the domain points to the new server, confirm that the website loads using HTTPS and that browsers do not show a certificate warning. Check both the main domain and the version using “www”, if your website supports both.

Review WordPress administrator accounts, remove access that is no longer needed and change passwords if account access has been shared widely. Confirm that backups, updates and security settings are enabled according to your chosen hosting arrangement.

Moving providers is not a reason to promise perfect security. It is an opportunity to establish sensible controls: strong unique passwords, restricted administrator access, regular backups and timely software updates.

Step 7: Monitor the old and new accounts

After the DNS change, monitor the website, contact forms and email. Look for missing images, error messages, failed payments, unusual redirects and customer reports.

Keep the old hosting account active until you are satisfied that the new website and email are working consistently. Cancelling too early can remove your fallback copy and make it harder to recover missing files or messages.

Once the migration is confirmed, save the new account details and document who owns the domain, where backups are stored and when hosting and domain renewals are due. This information should be accessible to the business rather than only to an individual contractor.

When to handle the migration yourself

A technically confident website owner may be able to move a small static website with a straightforward file transfer. A simple WordPress website may also be manageable with a reliable backup and migration tool.

Consider getting help when the website has a large database, online payments, many email accounts, custom applications, high traffic or little tolerance for downtime. Managed WordPress support or practical assistance from a hosting provider can make the process clearer and reduce avoidable errors.

A safer way to think about the move

Website migration is not simply a transfer from one server to another. It is a controlled change to a business system that customers use to find information, send enquiries, make purchases and judge credibility.

Back up first, prepare the new environment, test before changing DNS, protect email records and keep ownership access with the business. With that workflow, changing hosting providers becomes a manageable improvement rather than a rushed technical risk.

Your Cart

©2018 - currentyear Sonhosting • By Digital Nigeria - RC 7487481
All Rights Reserved
Powered by ShootOut Now Services