A Jamroom site is its files plus its database. Move both, then tell Jamroom where it is.
Moving to Jamroom Hosting? See the Jamroom Hosting chapter.
Copy the whole Jamroom directory to the new server, including the .htaccess files and the data directory. data/media holds your members' uploads and can be large.
If the files on the new server belong to a different user, check that the web server can still write to data and that the tools in modules/jrSystemTools/tools/ are executable (see Server Requirements).
Export the database on the old server, for example with mysqldump or phpMyAdmin, and import it into an empty database on the new server.
Developer Tools (ACP > Modules > Developer > Developer Tools > Tools > Database Admin) opens a database admin tool that can export and import too. For large sites, mysqldump on the command line is more reliable.
Edit data/config/config.php on the new server:
$_conf['jrCore_db_host'] = 'localhost';
$_conf['jrCore_db_port'] = '3306';
$_conf['jrCore_db_name'] = 'your_database';
$_conf['jrCore_db_user'] = 'your_db_user';
$_conf['jrCore_db_pass'] = 'your_db_password';
$_conf['jrCore_base_url'] = 'https://example.com';jrCore_base_url if the domain or directory changes. It's the full address of your site, without a slash at the end, for example https://example.com or https://example.com/community.Delete everything inside data/cache. Then log in as master admin and run:
When the new site works, point your domain's DNS at the new server.
To test changes on a copy of your live site, follow the same steps into a separate directory, database and address on your test server. You can leave out data/media if you don't need the uploads.
A test copy has your members' real email addresses and can send them email (notifications, password resets). Point its Delivery Method (ACP > Modules > Communication > Email Support > Global Config) at a mail server that doesn't deliver to the outside, and turn on Maintenance Mode so members can't log in to the copy.