Migration between orchestration platforms without operational disruption
Intwine helps service providers move between Cisco NSO and StratoWeave through phased, testable, and reversible migration strategies.
Whether you are moving selected services from Cisco NSO to StratoWeave, introducing StratoWeave alongside NSO, or designing services that could be implemented on either platform, Intwine focuses on preserving intent, reducing coupling, and protecting operational continuity.
Phase 1: Understand
- Inventory services, packages, devices, domains, integrations, and workflows
- Identify critical dependencies and operational exposure
- Map service intent to implementation behavior
Phase 2: Design
- Define the target architecture
- Choose the coexistence model
- Identify migration candidates
- Design service portability patterns
Phase 3: Prove
- Build the pilot
- Validate behavior
- Compare output and operational state
- Test rollback and failure handling
Phase 4: Migrate
- Move selected services or domains
- Integrate with OSS/BSS and operational systems
- Train operations teams
- Establish the support model
Phase 5: Optimize
- Reduce duplicated logic
- Improve service models
- Expand platform coverage where it creates value
- Use lessons learned to guide future domains
What makes the approach different
The goal is not code conversion for its own sake. The goal is to preserve service intent, reduce platform-specific coupling, and sequence change in a way that operations teams can actually absorb.
Email info@intwine.net to build a migration roadmap.