Moving an IWP control panel in not an impossible feat, but there are a few things to consider before taking any action.

One concern is not wanting to lose all of the current configurations for websites already set within an IWP control panel.

This scenario is the dilemma I recently encountered. I was using Infinite WP and had added an SSL (Secure Sockets Layer) to my website. An SSL is the standard security technology for establishing an encrypted link between a web server and a browser. The increased security of an SSL ensures that all data passed between the web server and any browsers remain private and structurally sound.

But because I had requested that the SSL apply to the entire domain, this caused some issues with a couple of sub-domains I had forgotten I had that were on the same cPanel. One such sub-domain, in particular, was the portal to my IWP control panel. Having more than 20 websites already configured in my IWP control panel, I needed to keep all of my IWP settings intact while at the same time move the entire system it to a new cPanel of its own.

There was another option I had to consider before coming up with the process of moving an IWP control panel at all. An easier approach might have been to apply the SSL to include the sub-domains. There are many different kinds of SSL’s offering various types of domain coverage. Unfortunately, the kind of SSL I had for the domain, would not allow this option to work and quickly removed this option from any course of action.

The second option was to install the sub-domains, including moving an IWP control panel sub-domain, to separate cPanels. Although creating individual cPanels would require a little more work, there were also some added benefits to this particular option.

Having domains, even sub-domains, on separate cPanels is considered to be more secure than having more than one site on any single cPanel. Furthermore, separate cPanels are easier to manage and make it less likely to upload files inadvertently to an incorrect location than if all the sites were on one cPanel.

I like having everything on separate cPanels making my choice in moving an IWP control panel, a more than acceptable alternative for my needs.

My Process for Moving an IWP Control PanelMoving an IWP control panel to new Domain on a cPanel

  1. On existing cPanel where your IWP is, go to PHPmyAdmin. Open (expand) the IWP database and Export an SQL file of its database.
  2. On existing cPanel go to File Manager and compress (zip) up your IWP folder.
  3. Download the zipped file to your desktop.
  4. Create new cPanel from your WHM for your IWP domain (sub-domain). NOTE: If you are going to use the same domain as you are currently using then you may name it anything other than what it is now named. Here are some alternate names to consider; Manage, Client-sites, Business, Maintenance, etc. ). If you use another domain, then you could still use the original name you used.
    If you have never before created a new account, here is a quick video tutorial describing how to do that.

  5. On new cPanel, create a new database (just like you do for a new WP install).
  6. Go into new cPanel PHPmyAdmin and Import the SQL file into the new database.
    The import can take some time as there is a lot of data in an IWP database. Just be patient. You can continue with the checklist in a separate tab or window while waiting for the import.
  7. On the new cPanel go to File Manager and create a new directory (folder). You can name it anything you like, including the same name you initially used for the subdirectory in your original installation.
  8. Upload the zipped IWP file to the new folder.
  9. Extract the files.
  10. Move the files to the new folder (they will have opened in an additional folder from the zip – again, just like when we upload a zipped WP install and have to move them to a level up.), i.e., Select All > move > (to the name of the new folder)
  11. Delete the Zipped file and the old folder
  12. In the new cPanel, open the config.php file and edit.
  13. Add new domain within the config.php file and add new database information > save
  14. Login with same credentials.
  15. If you have any premium add-ons – Go to Addons → Click the Check Now button and reconnect your add-ons to this panel.
  16. Test new install.
    Make sure you complete your testing process before continuing the checklist. You want to be sure your system is working as expected before you lose the access to the old installation.
  17. Update the domain associated with IWP account in LastPass (or other password management tool).
  18. In old cPanel File Manager, delete old directory folder.
  19. In old cPanel sub-domains, delete old sub-domain.
  20. In the old cPanel Databases, delete the old database.

Although this may look like a relatively long process, the time it took to complete was probably less than 15 minutes.

Once completed, the result is an entire IWP control panel ready for monitoring, checking and updating all of the sites that had already been configured and originally added to the IWP control panel.

What did you think of this tutorial? Your comments and replies are welcome below. Would you like to see more tutorials like this one? If so, contact me, and I would be happy to help you find the ultimate solution for any of your online challenges.

0 Shares

2 thoughts on “Moving an IWP Control Panel to a New Domain”

  1. Thanks Kerry! Great tutorial. I had a small snafu at first due to putting the new database prefix into the config.php file. I got an error when logging into iWP and that clued me in on examining the new database, which although the new db had the new db prefix, the imported tables still had the old prefix. So I changed that line in the config.php file and things seem ok now. The other thing I did differently was to just upload my zipped iWP folder into cPanel and then extracted it since I wanted to keep that same directory name (so I combined steps 7 and 8). All in all not as daunting as I had feared and as long as I have backups of the directory and the db it should be all right should I need to do this again or if something goes awry.

    1. You’re welcome, Marianne. Yes, any information you decided to change while creating the database needs to be exchanged and placed into the new config file. Nice adaptation realizing you wanted the same directory name. Many of these tasks seem daunting at first but as soon as you learn (by mistake or not) to understand the significance of the path and file structure it all falls into place quite nicely!

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.