As you are going through the steps to migrate your data into MantisHub, you'll get to a point where you need to look at preparing your data for migration.
Firstly, you'll need to contact support and we'll arrange a date for your migrations. We typically schedule migrations over the weekend to avoid service interruptions for your users.
You'll also need to provide the support team with a contact point and a method for getting your existing data to us. This could be via a OneDrive, Google Drive or Dropbox folder.
Next you'll need to get a dump of your database. Before doing this we suggest you disable inactive users that no longer need access to Mantis, which may reduce user pack costs for your MantisHub subscription. Note that you should disable inactive users and NOT delete them.
To create a dump of your database, run the following command. Remember to replace the parameters between the square brackets with your real values.
mysqldump -u [database_user] -p[database_password] [database_name] > [mysql_dump_file_path]
<image from mantisBT - can you provide one of dump command?>
Copy into your shared folder:
- A zip file of the MantisBT folder including all php files and all configuration files like config_inc.php, custom_strings_inc.php (optional), custom_constants_inc.php (optional), custom_relationships_inc.php (optional).
- A zip file for the MySQL dump.
- If attachments are not in the database dump and the MantisBT folder, then provided a zip file of the attachments folder.
- Code customizations
- Migration from databases other than MySQL.
- Migration from MantisBT versions older than v1.0.
- Use of deprecated features (e.g. news, project docs, FTP attachments).
- LDAP integration
- Custom plugins that are not offered by MantisHub.
Customizations done via configuration files and via the MantisBT web interface (e.g. custom fields), will be transferred to your MantisHub. Users will also be able to login to MantisHub with the same user names and passwords they previously used to access the migrated MantisBT.