We are a participant in the Amazon LLC Associates Program, an affiliate advertizing program designed to provide a means for us to earn fees by linking to Amazon.com and affiliated sites. Furthermore, this page may contain other sponsors, affiliate, and/or affiliate links. This means if you click on a link (ad) on our site, we may receive and commision. As always, opinions are my own and are sincere. You can read our disclaimer and private policy. We also have our disclosure policy.
I felt very released that now I can access my blog again. I just moved my hosting to ipage blindly. I mean I just did it without thinking any problems that I will face during the moving process. I thought that changing the nameserver in the domain panel in the old hosting and pointing the new server will get everything fine. Therefore, when I visited ipage.com, I just bought the hosting plan as soon as I finished comparing the feature with other hosting companies. All features looked great and the price was really interesting (fortunately I got the promo at that time, and now it is still going on). At the same time, my old hosting was already crowded while I planned to get bigger. Although the promo was only for new customers and it didn't apply for renewal, I just took it.
Here were some steps that I did and how It happened:
- I purchased the hosting plan and added some additional features besides the main product. There wasn't any problem with this process. I just needed to compare and thought further regarding my choice.
- After purchasing the host, I added my domain that would be hosted in domain central.
- I made compressed back up file from the old hosting. It was *.tar.gz compressed. How silly I had been that I never made any backup file during previous period of hosting in my old hosting.
- I downloaded the backup file with filezilla and it took less than one hour. There wasn't any problem at all. I never did this before, so I just had to find out how to put the file to my own hard disk drive. It was through trial and error times, but I did it finally. I used filezilla:
- Host – my website url, user: direct admin old hosting account username, password: the direct admin old hosting password
- Drag the backup file from remote location to my hard disk location
- I didn't confident how to put my old file to the new hosting and where it should stay. I had a chat with ipage support for the first time and the lady who helped me suggest me to just upload in the home. I did it also with Filezilla:
- Host – ftp.ipage.com, user: ipage account username, password: ipage password
- Drag the backup file from My hard Disk to the root
- The process took 1 day total time. What a very great patience I needed. It was still lucky that I still could see my website in the browser, although I still could not update or change.
- Wow, 2 days was very long for me. Anyway it was over. I saw my backup file in the ipage file manager. I was ready to uncompress the backup file using the archieve gateway in the cpanel. I thought I just needed to point the nameserver to ipage in my domain registrar to get my website started soon as the file was uncompressed. Sadly, what I saw was still the same file with extension *gz. Where were the bunches of files? I got so nervous.
I consulted the support officer one more time. She helped me to get the backup folder into the right track with another folder on the root as it was in the old hosting. I didn't know what she did with the *.gz file. I guessed that she double uncompressed it.
- I pointed the folder where the hosted files stayed in the domain central
1. Log into the control panel with the account username and password.
2. Click on ‘Domain Central’ under the ‘Domain’ section.
3. Click on the domain name that you want to point to the subdirectory.
4. Click on ‘Pointers'.
5. Select ‘Subdirectory’ from the dropdown menu and enter the folder name.
6. Click on the ‘Save’ button.
- Then I return to the Domain Registrar to point ipage as my server where I parked the domain. I change the name server into ns1.ipage.com and ns2.ipage.com
- What a great misery right now that I could not see my blog for 24-48 hours. I waited for 48 hours but nothing turn up. It just appeared: Error Establishing Database. I was very panic.
- I contacted the support department for the third time. She guided me very patiently to move the database to ipage. My goodness, I was very blind with internet, database, codes, etc. I tried two different database moved successfully in the new hosting.
- Export the database from myphpadmin in the old hosting to my hard disk.
- Make the same database name in MySQL in cpanel and import the SQL files to ipage.
It sounds very easy to say, but I went through trial and error as I moved the wrong database bunches of files that it made me almost cried. I had to redo the same process again.
Finally, here it comes my same blog parked in the new domain, ipage.com, My greatest empression so far was the fast, patient and clear service and guidance from the support department. Even I didn't have any backround knowledge in phpadmin and any coding things, I could make the migration well with their help. All support console questions were answered for 2 hours approximately so far.
I do really recommended it with all my heart to those who want to start blogging and to migrate site. If you have any questions so far that I might be able to help, please contact me.