Details Required for Migration to Windows Server with IIS, SolidCP/Plesk

1. Server & Hosting Account Details

• Current Hosting Provider Details

  • Control Panel: (e.g., DotNetPanel, Plesk, SolidCP, cPanel, DirectAdmin)

  • Server OS & Version: (e.g., Windows Server 2008, IIS 7)

  • Hosting Type: (Shared, VPS, Dedicated, Cloud)

• Admin/Root Access

  • RDP (Remote Desktop Protocol) for full access (if applicable)

  • Control panel login credentials (Plesk, SolidCP, DotNetPanel, etc.)

  • FTP/SFTP login details

• Domain & DNS Details

  • Domain registrar details (to update nameservers, if needed)

  • Current DNS settings (A, MX, CNAME, TXT records)

2. Website & Application Details

• Website Information

  • List of domains/subdomains to migrate

  • Website CMS or framework (WordPress, Joomla, .NET, PHP, custom)

  • Application dependencies (e.g., specific .NET versions, PHP versions, third-party modules)

• File & Data Migration

  • FTP/SFTP credentials

  • List of large files/folders (if applicable)

3. Database Details

• Database Information

  • Type of database (SQL Server, MySQL, MariaDB, PostgreSQL)

  • Database name(s)

  • Database credentials (username & password)

• Backup & Restore Plan

  • Do you have recent backups, or do we need to take them?

  • Preferred backup format (e.g., .bak for SQL Server, .sql for MySQL)

4. Email & FTP Details

• Email Accounts & Settings

  • Email provider (if hosted externally, e.g., Microsoft 365, Google Workspace)

  • Email accounts to migrate (list of email IDs)

  • SMTP/IMAP/POP settings

• FTP Accounts

  • List of FTP accounts & credentials

  • Permissions required for each FTP account

5. Custom Configuration & Additional Requirements

• SSL Certificates

  • Are there existing SSL certificates?

  • Do they need to be reinstalled or reissued?

• Cron Jobs / Scheduled Tasks

  • List of scheduled jobs running on the old server

• Third-Party Integrations

  • Any APIs, external services, or payment gateways connected to your application

• Testing & Go-Live Plan

  • Preferred testing period before switching DNS

  • Rollback plan in case of migration issues

6. Post-Migration Requirements

• Performance Testing

  • Website & application testing post-migration

  • Database integrity check

• Security & Optimization

  • Firewall rules, security hardening, and performance tuning

• Support Contact Details

  • Preferred contact for migration updates

  • Emergency contact details

Next Steps:

Once you provide these details, our team will:

1. Assess the current setup

2. Prepare a migration plan

3. Schedule and execute the migration with minimal downtime

4. Conduct post-migration testing and optimizations