Skip to main content

Quick Navigation

Migration Process Overview

Data migration in TestAuto2 follows a structured pattern to ensure traceability and compliance:

Available Migration Guides

Import Hazards from Excel — Extract HAZID or HARA data from spreadsheets and create hazard work items in Polarion with automated severity, exposure, and ASIL classification. Import FMEA from Excel — Move System FMEA, Design FMEA, or Process FMEA tables from Excel into TestAuto2 risksheets with automatic severity-occurrence-detection (S-O-D) scoring. Migrate from Legacy System — Plan and execute a full data migration from non-Polarion safety systems, including traceability reconstruction, data validation, and rollback procedures.

Key Considerations

Always validate imported data against TestAuto2 enumerations (ASIL values, severity scales, occurrence ratings) before publishing. Mismatched values can break downstream traceability and compliance reporting.
Perform a pilot migration on a test project before migrating production data. This allows you to refine your data mapping and identify issues early.
Legacy systems may not have explicit link metadata. Plan to rebuild traceability relationships using the Establish Traceability Links workflow after data import.