The Yahrtzeit Spreadsheet That Outgrew Itself: A Synagogue's Migration to Merkaz
We first heard about this project from a reader in the Midwest — a volunteer ritual coordinator at a 240-household Conservative synagogue who asked to stay anonymous. Her problem wasn't spiritual. It was logistical. For eleven years, the congregation had tracked yahrtzeit dates, Shabbat service assignments, and member lifecycle events in a color-coded Excel workbook passed between three volunteers like a family heirloom. When the last steward retired in early 2023, the workbook went with her. Nobody else understood its formulas.
That's the moment the board started shopping for synagogue management software in earnest. They looked at generic CRMs, a few church-oriented tools, and one or two Jewish community platforms. What they chose — and what we followed for the next fourteen months — was Merkaz, a community-management platform built around the rhythms of Jewish communal life: Hebrew calendars, yahrtzeit reminders, Shabbat-aware scheduling, and member CRM in one integrated system. This is the post-mortem of that migration, with the numbers the coordinator was willing to share.
The decision point: one calendar or three
The old system used three overlapping calendars — a Gregorian wall calendar in the office, a Hebrew-date column in the spreadsheet, and a mental map in the cantor's head. The board's first instinct was to buy a standalone Hebrew calendar app and keep the spreadsheet for everything else. The coordinator pushed back. "The whole reason we lose yahrtzeits," she told us, "is that the date lives in one place and the person lives in another."
What tipped the decision was a test they ran on a Thursday afternoon: they asked four volunteers to find the next yahrtzeit for a specific member and then find that member's phone number. Average time across the four: just over six minutes. The same lookup inside Merkaz, once the member records were imported, took under 30 seconds. That gap — call it five and a half minutes per lookup, multiplied across a year of Shabbat announcements, shiva notices, and yizkor mailings — was the argument that ended the debate.
Importing eleven years of grief and joy
The migration itself was messier than anyone expected. The spreadsheet had 1,847 rows, but roughly 200 of them were duplicates or half-finished entries. Hebrew dates had been entered in three different formats. Some yahrtzeit records listed only a first name. The coordinator spent six weeks cleaning data before the import — a phase she now calls "the part nobody warns you about."
Two obstacles stood out. First, Shabbat scheduling: the congregation needed reminders to pause between sundown Friday and Havdalah, and the first configuration they tried sent automated emails straight through Shabbat. Fixing that required rethinking which notifications were time-critical and which could wait until Saturday night. Second, the member CRM had to reconcile with the synagogue's separate donation ledger — a system nobody wanted to touch mid-year. They ended up running both in parallel for one full fiscal quarter before cutting over.
What actually changed
- Yahrtzeit reminders now go out automatically, timed to the Hebrew date, with a configurable lead time so families receive notice before the anniversary, not on it.
- Shabbat-aware scheduling stopped the drip of Friday-night and Saturday-morning auto-emails that had annoyed members for years.
- Member CRM consolidated contact history, lifecycle events, and volunteer roles into a single record — the spreadsheet's three-tab workaround is gone.
- New-member onboarding dropped from a two-week back-and-forth to a single intake form that populates the CRM directly.
The measurable results, fourteen months in
The coordinator shared four numbers. Yahrtzeit reminder delivery went from roughly 60 percent (the spreadsheet depended on whoever remembered to check it) to 98 percent. Volunteer hours spent on scheduling dropped from an estimated 12 per month to 3. Duplicate member records fell from about 200 to fewer than 15 after cleanup. And the congregation's yizkor mailing list — once assembled by hand each year — now exports in a single click.
Not everything improved. The board still keeps a paper backup of yahrtzeit dates, a habit the coordinator defends: "Software fails. Memory fails differently." Two older members never fully adopted the member portal and still call the office, which is fine — the office no longer has to call them back with answers.
What we take from this
This wasn't a story about technology replacing ritual. It was a story about a community outgrowing a tool that had served it well and then stopped. The migration took longer than the vendor's sales deck suggested, cost more volunteer hours than anyone budgeted, and required one stubborn coordinator who refused to let the Hebrew dates get mangled. But the outcome is quieter and better: families get their reminders on time, volunteers stop burning weekends on spreadsheets, and the person who used to hold it all in her head can finally take a vacation.
If your congregation is still running yahrtzeit reminders off a shared document, the lesson here isn't "buy software." It's "find out where the date lives and where the person lives, and put them in the same room." That's the whole project, really. Everything else is import cleanup.