Moving On From a Spreadsheet

Almost no church starts from nothing. By the time someone goes looking for a plugin like this, there’s already a system in place — it’s just an informal one. A shared inbox that three people have the password to and no one checks consistently. A notebook by the welcome desk. A spreadsheet started years ago by someone who’s since moved on, with columns nobody remembers the meaning of. The question that follows is a fair one: what happens to all of that?

Our honest answer is that we don’t import it, and that’s usually the right call rather than a limitation to work around. A prayer request carries a kind of consent with it — someone shared something on the understanding of who’d see it, at a particular moment, under whatever informal norms your church had at the time. Bulk-importing years of spreadsheet rows into a new system with its own visibility rules means making a decision on that person’s behalf about how their old, possibly forgotten request should now be handled. Most of the time, that’s not a decision anyone should be making quietly through a data migration.

What works better in practice is a clean cutover. Pick a date, start directing new requests to Lifted Prayers from that point forward, and let the old system finish out naturally rather than trying to merge it into the new one. If there are a handful of genuinely ongoing needs still active in the old system — someone your team is still walking with — those are worth re-entering by hand, deliberately, as new requests. That’s a few minutes of work for the requests that actually matter, rather than an automated import that treats a two-year-old spreadsheet row with the same weight as something submitted this morning.

There’s a secondary benefit to doing it this way that’s easy to miss upfront: it forces a real decision about who’s actually responsible for the queue going forward. Spreadsheets tend to survive because everyone assumes someone else is checking them. A moderation queue with one or two names attached to it doesn’t have that problem — silence in the queue is visible, not just assumed to be fine.

If your team truly has a large volume of active, still-relevant requests that need to move over, get in touch. It’s not something we automate, but it’s also not something we’ll leave you to sort out with a spreadsheet export and no help.