Setup checklist: export before access changes
Before ending a hosting relationship, save the reporting needed for editorial, client or sponsor obligations through the supported export route. Record the show, date range, timezone and metric definition with each file. A CSV without context can look precise while answering the wrong question. Keep personal or confidential information in an appropriate location rather than attaching it to an informal public migration checklist.
Do not join unlike totals silently
Different hosts and listening applications may use different filters or definitions. Put the migration date on charts and explain where the measurement source changes. If you combine periods for a business report, describe the limitation rather than presenting an apparently continuous series with no caveat. A sudden change at cutover may reflect measurement rather than a genuine shift in listeners.
Preserve useful granularity
Keep the level of detail you actually need: account, show, episode or date. An overall total may be insufficient to answer a later question about a particular release. At the same time, avoid collecting unnecessary personal records merely because an export option exists. Agree with the responsible organization on retention and access so the archive remains useful without becoming an unmanaged collection of sensitive material.
Rebuild the baseline honestly
After migration, start the new reporting period with a clear note about the source. Compare trends cautiously and use consistent windows going forward. Do not claim the new host recovered all history unless you have verified that specific capability and result. The practical goal is continuity of understanding, not a cosmetically smooth chart. A small explanation beside a graph is preferable to a misleading conclusion about audience growth or decline. A useful archive filename contains the show, source and covered dates. Keep the export’s original columns intact and perform any later calculations on a separate working copy.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Transistor import and migration guidance — Merchant documentation · support.transistor.fm · Merchant-controlled · checked 2026-09-19
- What a host download measures — Merchant documentation · support.transistor.fm · Merchant-controlled · checked 2026-09-19
- Historical analytics preservation during a move — Merchant documentation · support.transistor.fm · Merchant-controlled · checked 2026-09-19