TestRail Server to Cloud

Most customers would want to migrate to TestRail Cloud for the purpose of not having to maintain the instance. For example, on TestRail Cloud our team manages all instance maintenance, backups, and upgrades. However, there are some key differences to consider before migration.

Key differences between TestRail Server and TestRail Cloud

  1. API rate limit: TestRail Cloud has an API rate limit for performance. On TestRail Professional, the API rate limit is 180 requests per minute. On TestRail Enterprise it is 300 requests per minute. If you use heavy automation on TestRail Server this would be something to consider.
  2. Custom reports & defect plugins: Custom reports & custom defect plugins are only possible on TestRail Server, as access to the file system is required.
  3. Authentication methods: Authentication via AD/LDAP connections is currently only possible on TestRail Server. While SSO is possible on TestRail Cloud Enterprise via SAML 2.0, OAuth 2.0, OpenID Connect connections for authentication are not yet supported.
  4. Search performance: TestRail Cloud uses Elasticsearch for the Search functionality, which might be more performant for larger databases.
  5. MySQL vs SQL Server: While TestRail Server offers the flexibility to choose between MySQL and older versions of SQL Server, TestRail Cloud exclusively supports the latest stable version of MySQL (MySQL 8). This is an important consideration when making your choice.
  6. Backups: TestRail Cloud ensures regular backups of your data. This practice proves highly convenient for Disaster Recovery purposes. Additionally, Enterprise customers have the flexibility to choose their backup hours, minimizing any potential disruption to user activities.

 

Migrating from TestRail Server to TestRail Cloud

In order to migrate from TestRail Server to TestRail Cloud, please first reach out to our support team through the "Submit a request" link on the top right of this page or click here. We’ll need to ask some instance-specific questions to confirm the possibility to move your instance. In rare cases, it may not be possible to migrate to TestRail Cloud. In general, we would need the following to perform a migration:

  1. Set up and purchase your new TestRail Cloud subscription. Once it is ready, there is no need to add any data or users, as these will be overwritten when we migrate your existing database to the new instance. This can be done at any point in the process but is necessary prior to us restoring the contents of your installation.
  2. A MySQL database backup or SQL Server backup converted for use with MySQL is also required. If you’re using Cassandra for the Attachments, a Cassandra backup is also required. Read here how to get a MySQL and Cassandra backup:  Creating a TestRail backup documentation.
  3. A copy of your attachments & reports directories. You can find the directories in your settings under Administration > Data Management > Exports.

With the above provided to us, we can begin your migration to TestRail Cloud.

Note: If you’re not currently on a TestRail 7.x version our Support Team will need to upgrade prior to creating the data backup.

Was this article helpful?
13 out of 21 found this helpful