Import Data

Zeb
Zeb
  • Updated

Published Date: August 2026
Validated: Yes
Audience: Everyone
Products and Versions Covered: 

  • Onboarding Jama Connect®

Summary

Plan and coordinate the migration of existing work into Jama Connect® as part of your deployment. Determine what data needs to be imported, prepare it for migration, and establish a cutover plan that aligns data import with user training and access to Jama Connect.

Careful coordination helps minimize rework and prevents teams from working in multiple systems during the transition.

Resolution

Data migration should be planned as part of your overall Jama Connect deployment rather than treated as a separate activity. Use the process materials, existing content, and deployment scope identified during onboarding to determine what information should be moved into Jama Connect.

Determine What Data to Import

Review your existing work and determine which data needs to be migrated to Jama Connect.

Consider the process-related materials gathered earlier in onboarding and identify:

  • Existing work that must continue in Jama Connect.
  • In-flight projects or activities that need to be migrated.
  • Content needed to support your defined processes.
  • Data that should be retained for reference.
  • Data that does not need to be migrated.

Focus on importing content that supports the scope and goals of your deployment rather than moving existing data simply because it is available.

Prepare for the Data Import

Before importing data, confirm that your Jama Connect configuration is ready to support the content being migrated.

Review the data and determine how it will map to the appropriate Jama Connect structure and configuration.

Consider:

  • Item types and fields.
  • Relationships between items.
  • Project structure.
  • Required metadata.
  • Data quality and consistency.

Addressing these considerations before migration can help reduce cleanup and rework after the import.

Plan the Cutover

For in-flight work being migrated to Jama Connect, establish a clear cutover plan that defines when data will be moved and when users will begin working directly in Jama Connect.

Coordinate the cutover with:

  • Completion of the required Jama Connect configuration.
  • Data import activities.
  • User training.
  • User access to Jama Connect.
  • Communication to affected teams.

Clearly communicate when users should stop working in the previous system and begin working in Jama Connect.

Coordinate Import, Training, and Access

Align the data import closely with user training and Jama Connect access.

Avoid long periods between importing data and transitioning users to Jama Connect. If users continue updating information in the previous system after data has been migrated, teams may need to reconcile changes or repeat work.

Coordinating these activities helps ensure users are prepared to begin working with current data in Jama Connect at the appropriate time.

What to Do Next

Confirm that the required data has been identified and prepared, your Jama Connect configuration is ready, and the cutover schedule is coordinated with training, communication, and user access.

After the import, validate that the expected data is available and ready for users before transitioning the team to Jama Connect.

Additional Resources

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.