Exporting and Importing Projects from one IBM ELM Instance to another IBM ELM Instance with full history retention

As an ELM Platform Administrator and Project Manager,
I want a standardized, native, out-of-the-box utility (via the Web UI or a unified command-line tool) to export a complete Project Area (including requirements from DOORS Next, work items/SCM from EWM, and test artifacts from ETM) from one IBM ELM instance and import it into another completely independent IBM ELM instance .
So that we can seamlessly migrate, archive, or share projects without losing the full, legally required historical audit trail, change history, and traceability of our engineering artifacts .

 Why This is Useful (Business Justification)

Currently, the IBM ELM suite lacks a unified, native mechanism to move an entire, multi-application project area between distinct Jazz Team Servers (JTS). Organizations are forced to rely on complex, database-level migrations, server renames, or lossy workarounds like exporting to project templates, which alter asset IDs, break cross-application OSLC links, and discard histories .

A native, cross-instance project export/import tool is highly useful for the following scenarios:

Vendor and Partner Collaboration: Large-scale engineering organizations frequently need to hand over complete, self-contained project environments to external suppliers, or conversely, import a supplier's completed development project back into their primary ELM instance.

Mergers, Acquisitions, and Divestitures: When corporate structures change, project environments must be separated or consolidated. Without a native project-level migration tool, companies face massive, high-risk IT overhead to split or merge multi-terabyte databases.

Server Footprint & Performance Optimization: To maintain optimal server performance and manage storage costs, organizations need to "cold-archive" retired or completed projects. A simple file-based project export allows admins to safely remove projects from active servers and restore them on a dedicated archival ELM instance only if needed.

Overcoming Existing Limitations: Existing workarounds, such as standard migration templates, explicitly state that filters, baselines, and historical revisions are discarded . Furthermore, existing CLI capabilities (like repotools-ccm -scmExportComponent) are restricted to EWM SCM data, requiring complex command-line setups and ignoring the broader ELM requirements and test management context .