Migrating Sugar Instances to a New Box

[Jacob]

There is a forum post asking for help migrating. This is my response. Happy to get any feedback/enhancements. This will then migrate to wiki and/or the developer site.

Thanks,
Jacob

------------------------------------------

I just took a quick look and did not see good information out there.

Here is a quick summary of the steps that I would and have taken in the past:
1. Notify Users.
2. Synchronize all files to the new web server. rsync is a good command for this or xcopy on windows systems. You want to make sure you set it up so that you can run the command again later to update changed files.
3. Export the database. For MySQL the easiest command is mysqldump. This creates a big file that you can import on the other side. Most DBs will have an export function in their UIs. Write the output of the mysqldump command into a file.

mysqldump --opt mydatabase > sql.dump

4. Login to the new database and restore the backup file. You can either use the same web UI, or load the dump script from before. Inside the MySQL command line you can use'

\. sql.dump

If you started MySQL from the folder where you put sql.dump. One caution, if you run this file on the same server that you exported it from, you will loose all of your data.
5. Configure config.php on the new web server and make sure the system works well.
6. Stop the CRM system (block access to the folder is an affective way) to ensure there is no accidental use.
7. Re-run the file sync (make sure to copy your config.php from the new server to some other location and then copy it back, or reconfigure it after the file sync to point to the new database).
8. Re-run the database sync
9. Verify that the system is working as expected
10. Send the new URL to the users (or change the names erver to redirect the old URL).

If you happen to only be using MyISAM database tables and you are keeping on the same system architecture you can stop the MySQL engine, copy all of the files to the appropriate folder on the new database and then grant permissions to the new DB. MySQL will automatically look where the files should be.

I hope this helps.
Jacob

[ptemplin7]

Great start.

One thing I would add for all those newbies out there is a bit more coding. Like I've got the mysqldump into the .sql file. Now what are the ways to restore it. You give one there are others that may be easier to understand.

There are some other threads that give a good sequence. lets add a step by step procedure if possible.

Thanks Paris