Migrate to Rackspace IT Hosting dedicated server running Plesk

RACKSPACE SERVER
PRE-MIGRATION QUESTIONNAIRE & INFORMATION

The first step in assuring a timely and accurate migration is the information gathering stage. In order for us to provide an accurate quotation we would like as much information as possible.

Company Name:
Contact Name:
Contact Phone:		Fax:
Contact Email:

Rackspace Salesperson Name:

Existing Hosting Platform:
Total number of servers:
Current Provider:
Are you on a dedicated server or shared server (virtual dedicated)?
What Control Panel & Version (cPanel, Ensim, Plesk, Webmin, etc)?
If Plesk, total number of clients:
Total # of IP’s:		# of SSL Certs:
Are you running DNS on your server?
Do you have root level access?
Total server disk space:
Total number of domains / approx disk space/file size:
Total number of mail accounts to be migrated:
Total number of databases / approximate disk space/file size:
List of any known cron jobs to be configured:

Are there any other server applications such as Urchin, ChiliSoft, etc:

Are there any other server third-party applications, modules, dependencies or plug-ins:

Are there are special or custom configurations – this includes php.ini, httpd.conf or other custom configurations:

Are there any other special concerns or issues:

Our quote/proposal will be based upon the information provided. Failure to provide complete and accurate information may result in additional charges and / or problems with the migration.
Rackspace Platform:
Operating System:
Control Panel:
IF YOU ARE USING FRONTPAGE EXTENSIONS PLEASE READ THE NOTE BELOW Please be advised that Microsoft Frontpage is no longer a supported product. Microsoft Frontpage has been “end of lived” and Frontpage extensions are no longer available in new Plesk 8.1 (and later) installations. Sites/servers currently using Frontpage or Frontpage extensions may not be functional after migration. In most cases we will be able to install Frontpage extensions (if required) on your server but an additional fee will be charged. See the following URL for additional information: http://www.rtr.com/fpsupport
Do you require FrontPage?
SPECIAL NOTE REGARDING DNS Migrations will, in almost all cases, require DNS changes. We can not be held responsible for any required DNS changes for domains where you are not in control of the DNS. This means that the DNS must reside on the server to be migrated or managed through the Rackspace DNS Management Tool in the My.Rackspace portal. We strongly recommend that you switch your DNS to the Rackspace name servers and manage your DNS using the Rackspace DNS Management Tool in the My.Rackspace portal and that this change be done prior to the migration. For Plesk to Plesk migrations where you are hosting DNS on your own server there is the potential for DNS errors/corruption to occur during the migration. PHP / MYSQL VERSION COMPATIBILITY ISSUES There is the potential for version incompatibility (PHP, MySQL, etc) between your existing server and the new server. While Service Internet Solutions will do their best to point these out prior to migration, it is possible that some sites which use these applications may not function properly after migration. In addition, unless specifically noted, installation or debugging of any third party modules or dependencies required for scripts or other applications that are not part of the default Rackspace / Plesk install is not included in the migration. Debugging and / or updating of scripts is not included in the migration operation.
Please advise if there are any special PHP or MySQL configurations:

SPECIAL NOTE FOR NON PLESK TO PLESK MIGRATIONS If migrating to Plesk from something other than Plesk we will need to the following (these items can be supplied after engagement but are listed here to advise of the type and scope of information we will be requesting): Website hosting package / plan definition(s) (disc space, bandwidth, email, etc) Contact information for each domain owner/client who will have unique control panel access List of all email accounts, aliases, groups, redirects, etc and passwords (if available) by domain/client FTP username/password for each domain to be migrated (will use same information from existing platform if provided)