The domain name itself has nothing to do with the Suite Installation so Ill assume you mean you have purchased a new hosting package or server?
If so :
1.The first thing you want to do is get a dump of your SuiteCRM database.
2. Then import this into a database on your new hosting provider.
3. Make a backup of your entire Suite installation folder (create a tar.gz or zip file of it ). Also make sure you don’t copy non-suite files over.
4. Extract this into your hosting providers www folder or wherever your new host tells you.
5. Once you have extracted the files to your installation directory edit the config.php file and give it the new database credentials
e.g.
‘dbconfig’ =>
array (
‘db_host_name’ => ‘localhost’,
‘db_host_instance’ => ‘’,
‘db_user_name’ => ’ ',
‘db_password’ => ’ ‘,
‘db_name’ => ‘production…y’,
‘db_type’ => ’ l’,
You probably want to give it your new url as well: ‘site_url’ => ‘https://’,
You should now be able to login to Suite, So login and go to the admin panel then Repair then do a Quick Repair and rebuild, twice.
You should now be good to but you could have file permission issues etc if thats the case set permissions on your server as follows:
I followed your instructions and was met with the following error:
[b]Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@crm.1stintegrated.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.[/b]
You failed to mention in your steps that the poor guys needs to create the new database, since he is talking about a new domain and likely is using some panel like CPanel, which by default prepends a prefix on the databases identifying it with that domain’s account. Create a Database user and password as well, then associate that user with that database, giving them a set of permissions. THEN you can continue with the instructions given.