Migrating hosting providers

[Debunker13]

Recently my hosting provider went belly up.  I've managed to pull my DB and all the files I would normally use.  My question is now how do I get Blesta back up and running on this new site.  From what I gather I can use PhpMyAdmin within cPanel and export my old DB info and then import it into my new DB.  I'm trying to get a baseline best practice.  Has anyone here had to do this?  Or what other options do I have to get my data and company back operational.

I do not have access to the old site being hosted, I have a complete cPanel backup, including an individual MySQL backup.

[Tyson]

Moving an install typically requires 3 major steps:

1. Upload your current Blesta files from their old location to their new location
2. Create a new empty database on the new database server
3. Import your existing database tables onto the new database
   1. If your new database credentials differ from the old one, update them in /config/blesta.php

After that, you should be able to use Blesta as you normally would at the new location.

If you have reinstalled Blesta, you have not moved Blesta properly. Reinstalling Blesta generates a new system key that is used for all encryption and hashing. All existing encrypted and hashed data, such as credit card numbers, user passwords, settings, package meta, service fields, etc. have been lost.

[Michael]

Have you got the config/blesta.php you need that as it has the encryption / decryption key.

[Debunker13]

I’m sure that I do.  Where would I find it?  Blesta install directory?

[evolvewh]

It would be in public_html/config/

[Debunker13]

Actually after some fiddling I managed to hack the install.  Installed the same version of Blesta as in my old hosted space, replete with new database.  After reissuing my licence and completing the install, from phpMyAdmin dropped all tables then imported the tables and data exported from my previous install.  Had to request a password reset from the portal, but I’m now in and invoicing.  I spot checked about 5% of the client list, and I couldn’t find anything out of the ordinary.  All my YTD reports are the same, I’m going to say everything is as it should be. 

I don’t know just how true to form or best practice this is, but it works.  I’ve emailed my staff and customers to let them know they’ll have to request a password reset.  Which bring about a unique feature request, ability to mass reset passwords.

[Debunker13]

Tyson,

Thanks for the thorough step-by-step. 

In an odd twist of fate, I no longer use any of those additional functions you mentioned and I’ve migrate away from hosting as a whole, so concern about meta integrity is pretty moot.

For my purposes all that I need to is inform my staff they’ll need to update their passwords, and just re-authenticate my one payment portal. 

Thanks for the information and I will definitely use it in the future. 

[Beav]

If you use a different /config/blesta.php than before your system encrypt key is going to be different and can cause problems reading some information from database. Might be why you have to do password reset