You can identify all components of your current website to ensure a complete migration to Hostek. This process allows you to create a comprehensive checklist of files, databases, and email accounts so that no data is left behind during the move.
Before you begin
You will need:
Access to your current hosting control panel (e.g., cPanel, Plesk, or a custom dashboard).
Access to your current website's administrative dashboard (e.g., WordPress, Joomla, or Magento).
A list of all domains and subdomains currently associated with your site.
Inventory your website components
Identify all active domains and subdomains. List every domain name that currently points to your current host. This includes "www" and non-www versions, as well as any subdomains (e.g.,
blog.example.comorshop.example.com).List all website files and directories. Log into your current hosting account and identify the primary directory where your website files are stored (commonly
public_htmlorwww). Note any additional directories used for scripts, images, or assets.Identify all databases. List every database used by your website. If you use a CMS like WordPress, you will typically have at least one database. Note the specific database names and the associated usernames.
Inventory email accounts. List every email account currently hosted on your server. Record the full email addresses (e.g.,
[email protected]) and note if they use specific configurations like IMAP or POP3.Document third-party integrations. Identify any external services your site relies on, such as:
Payment gateways (e.g., PayPal, Stripe)
Marketing tools (e.g., Mailchimp)
External APIs or plugins
Social media integrations
Check for specialized software. Identify if your site uses specific software that requires unique configurations, such as:
ColdFusion or Lucee
Microsoft SQL Server
Specialized CMS plugins
Confirm the result
You have a complete list of every domain, subdomain, database, and email account that needs to be moved.
You have identified the specific paths and names of the files and databases required for the migration.
You have a clear understanding of any third-party services that require configuration updates after the move.
Limitations
This inventory process identifies the components that need to be moved but does not perform the actual migration of data. This step is intended to ensure that the migration plan is comprehensive before you begin moving files or changing DNS settings.
