Bringing your archive over
Point us at the podcast feed you already publish, or hand us a spreadsheet, and every recording in it is queued, transcribed, and waiting for your review.
Sources
A feed, a spreadsheet, or a manifest
- The podcast feed
- Paste its address into the dashboard. We take each entry’s audio, title, and date and show you the list, with anything you’ve already brought in left unchecked, and you choose what comes in. If your feed already carries every sermon you’ve preached, that’s the whole job.
- A spreadsheet
- A CSV of up to 5 MB, one row per sermon, with a link to where the recording already lives online and whatever else you have: title, date, speaker, series. Most old sermon systems can export one, and the dashboard has a template to start from.
- A manifest
- JSON sent to the management API, on Platform and Pro, for an archive that already lives in something structured and for the church whose volunteer is a programmer.
The run
Queued, retried, and charged once
Recordings are taken one at a time, and one that fails is tried up to five times. A run that stops halfway picks up where it left off, without charging twice for the same recording. You can close the page while it works.
If your rows are thin, tick the box and we’ll fill in a missing title, date, speaker, or series from the recording. Anything we fill in is flagged, because a guess about who preached shouldn’t go on a page under your church’s name until someone’s read it.
When the run finishes, one button publishes every sermon that came back with nothing flagged. The flagged ones wait for someone to open each and read it first.
| Sermon | Status |
|---|---|
| The Good Shepherd | Ready |
| Faith in the Furnace | Ready to review |
| Bread for the Journey | Ready |
| Advent Sunday, 2011 | Ready to review |
The import screen in the dashboard, partway through an example run.
Credits
An import spends backfill credits, never your month
Each imported sermon-equivalent draws one credit from a pool your plan grants once. Your monthly allowance is untouched, so bringing over twenty years doesn’t cost you this Sunday. If the credits run out partway, the import pauses, and everything already imported stays in your library.
Before you start
Three hours, and the sermon alone
- A recording over three hours is refused, and no credit is spent on it. A row that gives a longer length is refused before anything runs. For everything else, every feed included, we read the length from the file itself before transcribing it: MP3, M4A, WAV, and Ogg files all say. A file that doesn’t, like raw AAC, is refused as it’s transcribed instead, still without a charge. Either way it errors with a reason and the rest of the run carries on.
- Point us at sermon-only recordings. We transcribe everything in the file, so a full-service recording puts the welcome, the readings, the announcements, and the singing in the transcript, and spends credits on all of it. We don’t screen recordings, so what a church imports and publishes is its own decision. If the cut you publish as a podcast is sermon-only, that’s the feed to use.
Before a big import, we’ll look at a sample of your rows with you and tell you what it’ll cost in credits.
Tell us about your church
Put the size of your archive on the application, and we’ll work out the credits it needs with you.