> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/grow-and-monetize/monetization/authorize-and-execute-cutover.md). # Authorize and execute cutover Move an approved migration to the new delivery authority at an exact, verified boundary. Podigee Audio Video Ad Server lets an authorized operator move a migration from the current delivery authority to Podigee Ad Server. The cutover changes which delivery path serves the selected scope. It does not require a new RSS feed or a new episode identity. Use this task only after import, synthetic delivery checks, shadow comparison, and parity review are complete. A cutover is a live change. Stop when any required evidence is missing or uncertain. ## Before you start * You are the migration owner or have permission to execute a cutover. * The migration project is **Cutover ready**. * The current and target delivery routes are identified by exact versions and digests. * The target has a verified authority epoch and a tested rollback route. * The parity result has no blocking finding, or every difference has an approved decision. * The required review is complete. If your workspace permits solo confirmation, use it only when the displayed rule allows it. * You have a listener-safe effective time and a person responsible for watching the result. Do not cut over because a candidate is configured or because a player test succeeded. The cutover needs a complete authority, route, evidence, and rollback boundary. ## Review the migration state 1. Open **Monetization > Revenue jobs**. 2. Select **Migration and portability**. 3. Open the migration project. 4. Confirm **Cutover ready**. 5. Review the source and candidate release, parity result, blocking findings, current authority, target authority, rollback plan, and exact scope. If the project is **Blocked**, **Imported inactive**, or **Parity checking**, stop and return to the missing step. Do not force the action from another page. ## Open and authorize the cutover 1. Select **Switch delivery**. 2. In **Switch delivery at**, choose now or a planned transition time. 3. Review the podcast and episode scope, route, authority version, parity evidence, and rollback reference. 4. Complete the required review or confirmation for the workspace. 5. Select **Authorize and switch delivery**. Podigee binds the operation to the migration project revision, authority version, route digest, rollback plan, effective time, and review evidence. A future time creates a scheduled transition. It does not make the new route live early. ## Verify the live boundary When the operation completes, check: * The migration state is **Podigee Ad Server active**. * The selected authority is active for the exact podcast scope. * The previous authority remains available as the verified rollback route. * The RSS feed and episode identity are unchanged. * New requests use the target delivery path after the effective time. * Audio, video, HLS, analytics, and commercial evidence identify the active authority. * No duplicate billing or double-counted delivery appears at the boundary. ![The current One Podigee Integrations page shows Harbor and Pine Business Review live on the Podigee Ad Server, with recovery verification still required before the return control becomes available.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-ac992861d771198c9c4ac80b118635f5faed9e5c%2Fdoc-monetization-055-active-verification-needed.png?alt=media) *A live show does not offer an unverified return action.* ![The current One Podigee Launch readiness page shows an Active delivery state with controls to pause new ad decisions, roll back, or revoke the Campaign.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-0f74b77e5b511a108476ac120aa6b75354fe2d85%2Fdoc-monetization-061-live-delivery-active.png?alt=media) *The displayed state is the last state that Podigee confirmed with the delivery system.* ## Watch the first delivery evidence Review the first post-cutover requests and reports for the selected scope: * The request uses the new authority and exact release. * The decision, media, cache, and event records agree. * RSS audio remains reachable and the expected HLS variants remain valid. * Analytics records the correct delivery boundary. * Campaign delivery and money evidence remain single-counted. * No unexpected no-fill, fallback, or provider error appears. Keep the current authority available until this first evidence review is complete. ## If cutover is scheduled Before the effective time: 1. Recheck that the target release, route, rollback plan, and review have not changed. 2. Confirm the migration project still shows **Cutover ready**. 3. Cancel or reschedule the transition if any evidence expires or a blocking finding appears. At the effective time, Podigee activates the prepared authority boundary. A changed project or authority causes the transition to stop instead of combining old and new state. ## If Podigee blocks the action * **The project is not Cutover ready:** complete import and parity work first. * **A blocking finding remains:** resolve it or record the approved exception before you retry. * **The authority version changed:** prepare a new exact authority reference and repeat the review. * **The route digest does not match:** do not continue. Re-run the candidate and parity checks. * **The rollback plan is missing:** prepare and verify a rollback route. * **The review is missing or expired:** complete the required review again. * **The effective time is invalid:** choose a valid current or future boundary. * **A late callback or provider result is uncertain:** keep the current authority live and open an operational issue. ## If delivery evidence disagrees Stop new migration actions and preserve the exact request, authority, release, event, and commercial evidence. Do not repair the disagreement by editing a report or by switching the RSS feed. Use the rollback task only after the rollback owner confirms that the last verified route is ready. ## Expected result The selected podcast scope now uses the approved target delivery authority at one exact boundary. The RSS feed and episode identity remain stable, the previous authority remains available for a safe return, and the first delivery, analytics, and money evidence agrees. ## Next useful tasks Use the rollback task when the cutover fails or listener delivery is not safe. Use [Understand dynamic ad delivery in RSS audio](/documentation/grow-and-monetize/monetization/understand-dynamic-ad-delivery-in-rss-audio.md) to explain the request-time delivery path to your team. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.podigee.com/documentation/grow-and-monetize/monetization/authorize-and-execute-cutover.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.