Choose Your Path
Select the migration path that matches your situation:
Migrate from 2015 Core conformance to 2026 Content Register. Minimal changes required.
When to Use
- Your register used 2015 Core conformance only
- Simple content management without formal governance
- Internal use without external stakeholders
- Quick migration is priority
What You Get
- Basic register functionality
- Object identifiers
- Basic status dimensions
- Simple versioning
- Technology freedom
What You Don't Get
- Formal governance processes
- Concept plane capabilities
- Commitments framework
- Proposal workflow
Migration Steps
- Update terminology
Replace deprecated terms, adopt new terminology
1-2 days - Migrate status model
Convert single status to status dimensions
2-3 days - Update version model
Add major/minor version structure
1 day - Remove XML dependencies
If using normative schema, decouple
1-2 days - Test and validate
Verify migration correctness
2-3 days
Total Effort: ~1-2 weeks
Migrate from 2015 Extended conformance to 2026 Governed Content Register. Direct equivalent with new requirements.
When to Use
- Your register used 2015 Extended conformance
- Formal governance with control body
- Proposal management required
- External stakeholders involved
What You Get
- All Content Register features
- Full governance processes
- Proposal workflow
- Commitments framework
- Register specification
New Requirements
- Formal register specification document
- Commitments declaration
- Updated role names
- Process documentation
Migration Steps
- Update terminology
Replace deprecated terms, adopt new terminology
1-2 days - Migrate status model
Convert single status to status dimensions
2-3 days - Update version model
Add major/minor version structure
1 day - Update governance model
Rename roles, update processes
2-3 days - Create register specification
Document all required elements
3-5 days - Declare commitments
Determine and document commitment levels
1-2 days - Update change tracking
Migrate to Change objects
2-3 days - Test and validate
Verify migration correctness
3-5 days
Total Effort: ~2-4 weeks
Migrate from 2015 Hierarchical conformance to 2026 Governed Concept Register. Adds concept plane capabilities.
When to Use
- Your register used 2015 Hierarchical conformance
- You need concept hierarchy capabilities
- Semantic relationships are important
- Future-proofing for advanced features
What You Get
- All Governed Content features
- Explicit concept plane
- Concept versions
- Concept relations
- Two-plane architecture
Key Challenges
- Extracting concepts from existing content
- Implementing concept plane
- Linking content to concepts
- More complex data model
Migration Steps
- Update terminology
Replace deprecated terms, adopt new terminology
1-2 days - Migrate status model
Convert single status to status dimensions
2-3 days - Extract concepts
Identify and extract concepts from existing content
1-2 weeks - Implement concept plane
Create concept management infrastructure
1-2 weeks - Link content to concepts
Establish concept-content relationships
3-5 days - Update governance model
Add concept governance processes
3-5 days - Create register specification
Include concept organization system
3-5 days - Test and validate
Verify both planes work correctly
1 week
Total Effort: ~4-8 weeks
Full FERIN implementation with all capabilities including inheritance, composition, and concept domains.
When to Use
- Maximum capability needed
- Complex concept hierarchies
- Inheritance between concepts
- Partitive relationships important
- Concept domain management
What You Get
- All Governed Concept features
- Concept inheritance
- Partitive concepts
- Concept domains
- Concept composition
- Definition migration
Key Challenges
- Complex data model implementation
- Inheritance rule processing
- Composition management
- Most testing required
Migration Steps
- Complete Path C first
Establish Governed Concept Register
4-8 weeks - Implement inheritance
Add property inheritance between concepts
1-2 weeks - Implement composition
Add partitive relationship support
1 week - Implement concept domains
Add domain management capabilities
1 week - Implement definition migration
Support concept definition changes
1 week - Comprehensive testing
Test all advanced features
2 weeks
Total Effort: ~10-16 weeks
Path Comparison
| Feature | Path A | Path B | Path C | Path D |
|---|
| Content management | ✓ | ✓ | ✓ | ✓ |
| Governance processes | — | ✓ | ✓ | ✓ |
| Concept plane | — | — | ✓ | ✓ |
| Concept relations | — | — | Basic | Full |
| Concept inheritance | — | — | — | ✓ |
| Commitments | — | ✓ | ✓ | ✓ |
| Typical effort | 1-2 weeks | 2-4 weeks | 4-8 weeks | 10-16 weeks |
