Migrating data to DOORS Next
Before you begin
To migrate data, you must upgrade the IBM Engineering Requirements Management DOORS (DOORS) client where you do these migration tasks to version 9.6.1.3 or later.
About this task
DOORS Next provides a web browser-based alternative to the thick client installation and maintenance that is associated with DOORS. As part of the IBM IBM Collaborative Lifecycle Management on Cloud (ELM), DOORS Next provides a rich, highly collaborative environment for integration, common administration, traceability, and reporting. For more information, see Overview of DOORS Next. To take advantage of these capabilities, your team might choose to migrate some existing DOORS modules to DOORS Next. You can migrate data selectively and incrementally over an extended period as you identify project content that can benefit from the capabilities in DOORS Next.
You can migrate modules from DOORS to DOORS Next. This one-way migration moves requirements management into the ELM environment. Historical data is not migrated; however, the migration creates links in DOORS Next that link back to the corresponding records in DOORS. The links provides access to history, baselines, and other non-migrated data. By migrating only current data, you preserve all history and audit information in DOORS and eliminate the cost of migrating and revalidating audits and historical data in DOORS Next.
- One-way. The data is permanently moved to DOORS Next and is not intended to be exchanged or updated.
- Non-destructive. The default solution does not require data modification or deletion.
- Incremental. You can include one or more modules in a migration package with minimal disruption to an entire project.
- Simple. Migration is series of export and import operations with minimal manual steps.
- Optimized. The migration automatically harmonizes your module type systems and creates corresponding artifact types in DOORS Next.
- Safe. After you export a migration package, the corresponding data is locked in DOORS to prevent further editing.
- Complete. All of your important DOORS data is considered, including folders, modules, objects, views, and links.
- Project structure
- Attributes and types
- Attribute DXL and Layout DXL content as calculated values
- Views
- Tables as XHTML renderings
- Internal links
- Outbound OSLC links
- External links to web URLs
- OLE objects
- Pictures
- Text styling, such as bold, italic, and underline
One or more modules can be included in a migration package. Only the current version of modules is migrated. Because the migration of project data can be incremental, do not assume that you need to migrate everything. Migrate only data that is relevant in the context of your business needs and DOORS Next. By focusing on necessary data only, you can reduce effort, disruption, and cost. This approach also prevents the proliferation of irrelevant data in DOORS Next.
Treat migrated data as read-only during the migration process. Maintain the locks on migrated data in DOORS after a package is exported to avoid conflicting changes in both tools. Unlock only data if the migration process is abandoned.