This guide explains how to manually migrate live encoders and live channels from Zype Live 1 to Zype Live 3.
Most customers will experience a seamless or Zype-assisted migration. However, some customers—particularly those with custom ingest workflows, strict maintenance windows, or operational constraints—may prefer to manage the migration themselves.
This article covers:
When manual migration is appropriate
How to configure Live 3 encoders correctly
How hostnames and DNS behave during migration
How to migrate scheduled events and 24/7 linear channels
What to do once migration is complete
Important Zype Live 1 encoders cannot be deleted by customers. Decommissioning is handled by Zype Support after migration is confirmed.
When to Use Manual Migration
Manual migration may be appropriate if you:
Need to control the exact timing of encoder cutover
Are migrating a subset of channels first
Have strict maintenance or blackout windows
Want to validate Live 3 behavior before full cutover
If you prefer Zype to manage migration for you, see Zype-Managed Migration at the end of this article.
Key Concept: Hostnames and DNS During Migration
Using the Same Hostname as Live 1
In a hard cutover scenario (where Live 1 is fully stopped before Live 3 starts), Live 3 encoders can be configured using the same hostname as the existing Live 1 encoder. This is the recommended approach.
This ensures:
Existing ingest configurations continue to work
No upstream encoder changes are required
Downstream playback and routing remain intact
Live 1 Encoder Name
Live 3 Encoder Name
Will This Cause a DNS Conflict?
No.
Although it may appear that creating a Live 3 encoder with the same hostname could cause a DNS conflict, this is handled automatically by Zype.
What actually happens:
When the Live 3 encoder is created, the hostname is registered
When the Live 3 rendering pipeline runs, Zype updates the underlying DNS records
The Live 3 hostname mapping overrides the Live 1 mapping
There is no customer-managed DNS involved and no risk of hostname collision when following this process.
Important Exception: Running Live 1 and Live 3 in Parallel
If you need to keep a Live 1 encoder active while validating Live 3, you must use a different hostname when creating the Live 3 encoder.
This allows both encoders to coexist temporarily and is commonly used for:
24/7 linear channels
Parallel streaming validation
Zero-downtime cutovers
Parallel operation should be short-lived and only used during transition.
Manual Migration Steps
Step 1: Create a New Live 3 Encoder
Navigate to Live > Manage Encoders (Live 3) in Zype Admin
Select Add Encoder
Configure the encoder with:
Appropriate hostname (same or different, depending on strategy)
Matching region and capacity
Save and provision the encoder
Step 2: Validate Encoder Configuration
Before switching traffic:
Confirm the Live 3 encoder provisions successfully
Confirm ingest details are available
Verify DVR and event settings as needed
Do not start streaming yet if the Live 1 encoder is still active and sharing a hostname.
Step 3: Stop Using the Live 1 Encoder (Hard Cutover Only)
For hard cutovers:
Stop all streams on the Live 1 encoder
Do not restart or reuse Live 1 encoders
Begin streaming exclusively to Live 3
At this point:
Live 3 becomes the source of truth
DNS routing resolves to Live 3 automatically
Live 1 encoders should be considered retired
Step 4: Validate Live 3 Operation
After cutover:
Confirm live playback functions as expected
Validate DVR, Live Events, and archiving behavior
Confirm usage appears under Live 3 Encoder Hours in Usage Reports (updated within 24 hours)
Migrating an Existing 24/7 Linear Channel
The following steps apply specifically to always-on linear streams.
The goal is to replicate your existing Live 1 workflow in Live 3 while minimizing risk and downtime.
Overview of the Process
1. Create a New Live 3 Encoder
Create a new encoder under Live > Manage Encoders (Live 3)
Use a different hostname if you plan to run Live 1 and Live 3 in parallel
Custom hostnames are supported
2. Create a New Linear Live Event
Create a new Live Event in the CMS
Associate it with the new Live 3 encoder
Ensure the event is created as Linear (not On-Demand)
This event will replace the existing Live 1 event
Ingest Options
Option 1: Stream to Both Encoders (Recommended)
If your source can stream to multiple destinations:
Start streaming to the Live 3 encoder while keeping Live 1 active
Validate playback in the Live 3 preview and start the event
Update players or endpoints to reference the new Live 3 event
Once confirmed, stop streaming to Live 1
Decommission the old Live 1 event
Result: Little to no viewer downtime.
Option 2: Stream to One Encoder Only
If your source supports only one destination:
Fully configure the Live 3 encoder and Live Event in advance
Stop streaming to Live 1
Switch the source to stream into Live 3
Validate playback, start the event, and update CMS references
Expected downtime: Plan for up to 30 minutes, though actual interruption is often much shorter when prepared.
Important Notes for Linear Channels
Always validate Live 3 playback before directing viewers
Do not stop or remove the Live 1 event until Live 3 is confirmed
Double-check the event type is Linear
Avoid running Live 1 and Live 3 in parallel long-term
Decommissioning Live 1 Encoders
Customers cannot delete Live 1 encoders themselves.