Lesson 5.2 - Migration Protocol
Migration Protocol. If you've decided to switch streaming software, the structured migration to minimize downtime and lost work.
Pre-migration (days 1-7):
- Document your current setup in writing (scenes, sources, settings, hotkeys)
- Take screenshots of every scene at production quality
- Export current scene collection as JSON backup
- Export OBS settings (Output, Audio, Video, etc.) as documentation
- List every plugin you currently use and confirm equivalents exist in target software
Setup new software (days 8-10):
- Install new streaming software fresh
- Configure base settings (encoder, bitrate, resolution, framerate)
- Import or re-create your primary scene first (the one you use most)
- Add core sources (webcam, microphone, game capture)
- Test record
Iteration (days 11-13):
- Add additional scenes (Starting Soon, BRB, Ending)
- Configure alert browser sources
- Set up overlay branding elements
- Configure scene transitions
- Set up hotkeys to match your old setup (muscle memory matters)
- Test record again
Validation (day 14):
- Run a full-length test stream (not live — just record everything as if live)
- Check audio levels, video quality, scene transitions, alerts, chat overlay
- Compare to your old setup's recording for parity
- Fix any gaps
Go-live (day 15+):
- First live stream on new software during a low-stakes time slot
- Have a backup plan to revert to old software if issues arise mid-stream
- Communicate to audience: "first stream on new setup, expect some bumps"
2 weeks for a clean migration. Don't rush it.
