Hierarchy Migration
Migrate existing projects to new hierarchy configurations with our powerful migration wizard.
Overview
The Requirements Hierarchy Migration Wizard allows you to safely migrate existing projects to new hierarchy structures while preserving all FMEA relationships and data integrity. This tool is available for Advanced tier and above organizations, or for Super Admin users regardless of subscription tier.
Requirements Hierarchy Migration is available for:
- Super Admin users - Full access to all features regardless of organization tier
- Organization Admin users - Limited by their organization's subscription tier (Advanced+ required)
- Free/Basic tier organizations - No migration access for regular admins (but full admin functions available)
Contact support for tier upgrades or Super Admin access.
When to Use Hierarchy Migration
Consider hierarchy migration when you want to:
- Change requirement types (e.g., from 3-level to 5-level hierarchies)
- Reorganize hierarchy levels (reorder, rename, or restructure levels)
- Standardize across projects (apply consistent naming/abbreviations)
- Support method changes (e.g., updating acronyms or terminology)
- Migration creates a new project with the migrated data
- The original project remains unchanged and intact
- All FMEA analysis links are automatically preserved
- Migration can be performed on live projects
Accessing the Migration Wizard
- Login as an organization administrator or super admin
- Navigate to Admin Dashboard
- Click "Hierarchy Migration Wizard" button
- Ensure your organization has Advanced tier subscription, or you have super admin privileges
If you don't see the migration wizard, your organization may not have Advanced tier access or you may need super admin privileges. Contact our support team for assistance with tier upgrades or admin access.
Migration Wizard Steps
Step 1: Select Project
Choose which project you want to migrate by browsing the list of available projects:
- Project Cards: Each project displays name, description, and ID badge
- Search & Filter: Projects are filterable and searchable
- Current Status: View project membership and activity status
- Selection: Click to select your target project
Start with a smaller, non-critical project to familiarize yourself with the migration process.
Step 2: Configure Target Hierarchy
Design your new hierarchy structure:
Defining Hierarchy Levels
- Order: Assign sequential order to levels (1, 2, 3, etc.)
- Name: Full descriptive name (e.g., "Customer Requirement")
- Abbreviation: Short acronym (max 4 characters, e.g., "CR")
- Color: Visual color code for UI display
Managing Hierarchy Levels
- Add: "+" button adds new levels with default values
- Reorder: "↑" arrow moves levels up in the hierarchy
- Remove: "×" button deletes levels (minimum 1 level required)
- Edit: Direct field editing for instant updates
Use colors that clearly distinguish levels:
- Blue for customer/system levels
- Green for requirements
- Purple for functions
- Orange for testing
- Red for validation
Step 3: Preview Migration
Review the changes before execution:
Before & After Comparison
- Side-by-side view of current vs. target hierarchy
- Level mappings show how old levels translate to new ones
- Visual colors help distinguish hierarchy levels
Migration Impact Summary
Three key metrics show what will happen:
- Requirements Affected: Total requirements that need updating
- FMEA Links Preserved: Number of FMEA relationships maintained
- Deepest Level Affected: How deeply into the hierarchy changes extend
Always review the impact summary. If numbers seem unexpected, double-check your target hierarchy configuration.
Step 4: Confirm Migration
Final safety checkpoint before migration:
Important Safety Information
- ✅ New project creation (original remains unchanged)
- ✅ FMEA relationship preservation
- ✅ Incremental processing for large projects
- ✅ Option to share with team after migration
Migration Summary
- Source: Original project name and details
- Target: New project name (appends " (Migrated)")
- Timeline: Expected completion estimates
Step 5: Execute Migration
Monitor the migration process:
Progress Tracking
- Real-time animation shows current processing step
- Percentage completion with progress bar
- Step-by-step indicator of what's being processed
- Time estimates based on project size
Processing Steps
- Validation: Verifying migration parameters
- Project Creation: Setting up new project structure
- Data Migration: Transferring requirements and relationships
- FMEA Preservation: Maintaining analysis links
- Cleanup: Finalizing migration
Avoid closing the browser or refreshing during migration. Large projects may take several minutes.
Step 6: Migration Complete
Review results and next steps:
Migration Results
- Requirements Migrated: Count of successfully moved requirements
- Hierarchy Levels: Number of levels in new structure
- FMEA Preserved: Confirmation of analysis data integrity
- New Project ID: Unique identifier of migrated project
Next Steps Guidance
- Review the new project structure
- Verify FMEA relationships are intact
- Share the migrated project with team members
- Archive the original project if desired
Safety Features
Data Preservation
- Immutable Originals: Source projects remain completely unchanged
- FMEA Integrity: All failure mode and analysis relationships preserved
- Complete Cloning: All project data duplicated exactly (with new hierarchy)
Error Handling
- Graceful Failures: Failed migrations provide clear error messages
- Resume Capability: Partially failed migrations can be restarted
- Support Access: Direct support contact for migration issues
Permissions & Security
- Admin-Only: Only organization administrators can access migration
- Organization Scope: Users can only migrate their organization's projects
- Audit Logging: All migration actions are logged for compliance
Troubleshooting
Common Issues
"Migration Wizard Not Visible"
- Verify your organization has Advanced tier subscription, or you have Super Admin privileges
- Ensure you have admin or super admin role
- Check if the feature flag is enabled for your organization
Migration Takes Too Long
- Large projects (>500 requirements) naturally take time
- Check your internet connection stability
- Avoid running multiple migrations simultaneously
- Contact support if it exceeds 30 minutes
Unexpected Migration Results
- Verify your target hierarchy configuration
- Check that all required levels were defined
- Review the migration preview data carefully
Support & Contact
Need Help?
📧 Email Support: madhu.chellappa@gmail.com
Include in support request:
- Organization name and ID
- Project name and ID (if available)
- Step where issue occurred
- Error message or screenshot
- Browser and device information
For enterprise customers with service level agreements, priority support ensures rapid migration resolution.
Technical Details
Migration Architecture
- Backend Processing: Server-side migration using database transactions
- Real-time Updates: WebSocket connection for progress updates
- Rollback Support: Failed migrations automatically rollback changes
- Database Integrity: Foreign key constraints maintained throughout
Performance Considerations
- Batch Processing: Large projects processed in manageable chunks
- Memory Optimization: Efficient memory usage for large datasets
- Concurrent Safe: Multiple users can migrate different projects
Limitations & Restrictions
- Maximum 15 hierarchy levels per project
- Projects must have at least 1 hierarchy level
- Migration does not affect existing custom IDs
- Available for Advanced tier organizations and Super Admin users
Ready to migrate your requirement hierarchies? Access the Admin Dashboard to get started with safe, reliable project migration! 🚀