Connect On Premise to Cloud Migration Services - Checklist

By Eric posted 13 days ago

  

Jama Connect delivered via the cloud is an attractive option for organizations wanting to get up and running in a scalable, highly secure hosted environment. Cloud-based users receive more frequent enhancements and capability - several times per quarter. Version updates require little effort. By outsourcing to Jama’s cloud deployment, your organization avoids a host of technical distractions. The results free you and your business to focus on your product development. 

Here are the major steps and some key considerations for migrating your local installation of Jama Software to Jama Software's hosted service:

Prior to migration:

Customer

Jama Account
Manager

Jama Technical

Resource

 

X

X

 

Ensure your existing version of Jama On Premises is at least 2015.2 or higher.  Jama Software offers professional services to help upgrade if you need assistance. Talk to your Jama Account Manager for more information.

X

X

 

Together with your Jama Account Manager, identify the following:

·       Target date for migration completion and preferred timeline for project start

·       Preferred file transfer method (e.g. Sharepoint)

·       Existing Jama integrations

·       Existing custom reports

·       Existing LDAP

·       Need for SAML SSO (please note e-signatures capability is not supported with SSO)

·       Primary technical admin contact with Jama root and server file access

·       Preferred hosted URL (Jama Account Manager will validate availability)

X

 

 

Complete any required internal approvals to move your data to Jama Software’s hosted service and any contractual changes with Jama Software.

X

X

 

Sign conversion quote provided by your Jama Account Manager.

X

 

 

Secure access to an administrator (with Root access) who can obtain a backup of your Jama Software installation.

X

X

X

Schedule 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

 

 

Obtain backup of Jama Software when people are not using the system 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 for 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 identified during the dry run.



Migration Production run

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 (especially important if you are currently using an older version of Jama Software)

 

Jama’s Data Center: Jama’s SaaS infrastructure uses Amazon’s AWS EC3 platform.

One of the core reasons we use Amazon’s AWS EC2 platform is the wealth of security experience Amazon has amassed over the years in building and growing AWS. Amazon’s AWS EC2 Platform is the gold standard not only for cloud applications, but also for application and data security. Amazon has successfully completed many security audits and is certified for some of the strictest and thorough standards.

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

Availability

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

Data Storage & 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 60 days
0 comments
13 views