Deployment Migration vs. Data Migration for Jama Connect®

Zeb
Zeb
  • Updated

Author: Zeb Geary
Date: November 2025
Last Updated: January 2026
Audience: Jama Connect® Administration
Environment: All Supported Jama Connect® Instances

Use Case

Data needs to be migrated from one Jama Connect® system or project to another. This article explains the two primary approaches—Deployment Migration and Data Migration—distinguishes between them, and provides scenario-based recommendations for when to use each.

Deployment Migration: Appropriate when a complete database migration is required, and the source system’s data will overwrite the target system.

  • Example: Moving from Self-Hosted Jama Connect® → Cloud Jama Connect®.

Data Migration: Appropriate when migrating project-level data, where the target system’s data must remain intact.

  • Example: Two teams using separate Jama Connect® instances need to consolidate into a single system.

Best Practice

Deployment Migration:

  • Use for full database migrations where the target system will be replaced.

  • Minimal manual tasks; complete data restoration ensures zero loss.

Data Migration:

  • Use when migrating specific projects while preserving existing target system data.

  • Perform careful mapping of source to target to maintain process consistency.

  • Save/export regularly and follow a documented Export → Map → Import workflow.

Definitions

Deployment Migrations: 

  • Moves a complete Jama Connect® system from one deployment model to another.

    • On-Premises → Cloud

    • Cloud → CVC

    • Cloud / Customer Validated Cloud (CVC) → On-Premises

Data Migrations: Project-level migration using export/import tools. Preserves existing target data. Use cases include consolidating projects or migrating from legacy tools to Jama Connect®.

  • Transfers specific project data between Jama Connect® systems without overwriting target data.

  • Example: Consolidating Team A’s projects into Team B’s system.

  • It can also include migration from legacy tools like DOORS.

  • The source system may be discontinued after migration.

Approach Pros Cons Recommended Scenarios
Deployment Migration
  • Complete database restore results in zero data loss.
  • Process requires minimal manually tasks.
  • Target system is completely overwritten by source system (data loss if target system was in use).
  • Migration from On-Premises to Cloud
  • Migration from Cloud to Customer Validated Cloud
Data Migration
  • Target system is not overwritten by source.
  • Mapping from source to target enables transformation to processes supported by target system.
  • Data available for migration is limited to current Jama Connect project data. Does not include:
    • Versions/Baselines
    • Activity history
    • Reviews
    • Comments
    • Test Plans/Cycle/Runs
    • Data for certain fields types, e.g., Item of Type, User
  • Configuration and user information (Admin) not migrated.
  • Manual Export-Mapping-Import process.
  • Migration to an active Jama Connect system where data must not be overwritten.
  • Migration from a legacy tool to Jama Connect.

References

Feedback:
We welcome your input! Please leave any comments or suggestions below.

Related to

Was this article helpful?

0 out of 1 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.