Self-Hosted to Cloud Deployment Migration

Author: Dana Medhaug
Updated: January 2025
Audience: All Jama Connect® Users

Summary

Migrating to Jama Connect® Cloud offers organizations a scalable, secure, and low-maintenance environment. Cloud customers benefit from frequent feature releases—multiple times per quarter—with minimal effort required for updates. By moving to the cloud, your team can avoid technical overhead and focus more fully on product development.

This guide outlines the key steps and significant considerations for transitioning from a self-hosted Jama Connect deployment to Jama Software’s cloud service.

Before the Migration

The following table outlines responsibilities for each stakeholder involved in the migration preparation process:

Customer	Jama Success Manager	Jama Technical Resource
X	X		Ensure your existing version of Jama Self-Hosted is on a supported version Jama Software offers services to help upgrade if you need assistance Talk to your Jama Customer Success Manager for more information
X	X		Together with your Jama Success Manager, identify the following: The target date for migration completion and the preferred timeline for project start File transfer method SFTP Existing Jama integrations Existing custom reports Existing LDAP Need for SAML SSO Please note that e-signatures capability is not supported with SSO Primary technical admin contact with Jama root and server file access Preferred Cloud URL Jama Success Manager will validate the availability.
X			Complete any required internal approvals to move your data to Jama Software’s Cloud service and any contractual changes with Jama Software®.
X	X		Sign conversion quote provided by your Jama Success Manager
X			Secure access to an administrator (with Root access) who can obtain a backup of your Jama Software installation
X	X	X	Schedule an introduction call to the assigned Jama Technical Resource Audience to include your server administrator

Migration Production Run

Customer	Jama Account Manager	Jama Technical Resource
X			Put the application in maintenance mode, obtain a backup of Jama Software®, and send files to Jama Software via file share.
		X	Jama Technical resource will perform the migration into a sandbox instance and provide you with access to testing. Afterwards, they will also provide the estimated downtime for production instance migration and the new instance URL
X			UAT, approval, and production migration scheduling
X			Communicate your plan internally and ensure your end-users understand planned periods of system downtime that may be required to be identified during the dry run.

Final Migration Execution

Customer	Jama Account Manager	Jama Technical Resource
X			Enforce maintenance/outage window.
X		X	Production migration process as above
X			Consider running internal briefings to orient users This is especially important if you are currently using an older version of Jama Software

About Jama’s Cloud Infrastructure

Jama Connect’s SaaS infrastructure is hosted on Amazon Web Services (AWS EC2), widely regarded as the industry gold standard for cloud application performance and data security.

AWS brings:

Decades of proven cloud security experience
Compliance with some of the world’s most stringent security standards
Robust infrastructure for hosting secure, scalable enterprise applications

Migrating to Jama’s Cloud ensures your organization benefits from best-in-class security, high availability, and regular product enhancements.

Amazon provides resources to expand on its certifications and third-party audits. For details on AWS certifications and accreditation, you can visit aws.amazon.com/security.

Availability

Server uptime of 99.5%
Proactive notification of any scheduled maintenance
Scheduled upgrades, with advance customer notification (minimum 24 hours)

Data Storage and Security

Data-at-rest, in-motion, and leak protection
Security scans and firewall protection
Data transmission secured over HTTPS
Nightly full backups of the database
Nightly incremental and weekly full backups of file attachments
Backup rotation policy of sixty (60) days