Onboarding
Migrating from spreadsheets: a realistic four-week plan
Migrating a church off spreadsheets is rarely a technical problem. The data moves in an afternoon. The harder work is agreeing on what the records mean, who owns them, and how the team will keep them current after the switch. A four-week plan with one focus per week gives a small or midsize church a calmer way through the change. Week one is inventory. Week two is cleanup. Week three is import and access. Week four is the first real working week, with the spreadsheets archived but available.
By Congregation Portal · Published · Reviewed · Updated · ~7 min read
Why this migration usually stalls
- Migration stall
- A switch that gets to import but never to adoption, usually because the new system is treated as a copy of the old spreadsheets instead of a chance to define one source of truth.
Spreadsheets are easy to start and hard to leave because they encode a quiet set of team agreements. Who edits which column. What a blank cell means. Which sheet is the real one. Moving the data is mechanical. Moving the agreements is the actual project. The plan below assumes that and spends the first half of the month on agreements, not on imports.
Week one: inventory the spreadsheets you actually have
Most churches discover during week one that they have more spreadsheets than anyone realized. The goal of this week is not cleanup. It is honest visibility.
- Ask every staff member and key volunteer to list every sheet, document, or app they personally maintain for church records.
- For each sheet, capture its purpose, its owner, the last update date, and the number of rows.
- Tag each sheet as authoritative, partial duplicate, or stale.
- Identify any sheet that contains information that exists nowhere else. Those are the highest-risk items.
- Share the inventory with the leadership team in a single document. Surprises are normal.
Week two: cleanup before import, not after
Importing dirty data into a new platform creates the impression that the platform itself is messy. Spend a full week cleaning the source spreadsheets first. Resist the urge to redesign your data model during this week. Match what you already have. Improvements come later.
- Standardize household names and addresses, deduplicating where two rows describe the same household.
- Confirm primary contact email and phone for every household.
- Reconcile group rosters with the actual people currently attending those groups.
- Decide a single convention for visitor and member status, and apply it consistently.
- Archive any sheet that is no longer needed. Removing complexity is part of the migration.
An example: the women's ministry roster
One mid-sized congregation we worked with discovered four overlapping women's-ministry rosters during week one. Two were maintained by group leaders, one by the administrator, and one by a long-time volunteer. None matched. During week two, the team chose a single owner and merged the four rosters into one, dropping people who had not participated in eighteen months. The roster shrank by twenty-two percent and became immediately more useful. The migration itself in week three then moved one clean list instead of four contested ones.
Week three: import, configure access, train owners
By week three, the data is clean enough to move. Resist the temptation to spend the week perfecting layout. The priority is that the right people can do their own work in the new platform by the end of the week.
- Import households, then people, then groups, then attendance history if available.
- Configure roles to match real responsibilities, not the org chart on paper.
- Walk each ministry leader through their own roster live, not via recorded video.
- Identify the first two reports the leadership team will actually use, and confirm they work.
- Schedule a thirty-minute office-hours block twice during week four to catch friction early.
Week four: work in the new system, archive the old
Week four is the real test. The team does the week's actual work in the new platform. The spreadsheets are archived to a read-only folder so the team is not tempted to fall back. A short daily check in keeps friction visible.
| Old spreadsheet workflow | New platform workflow |
|---|---|
| Email the latest version weekly | Everyone reads the same live record |
| Wait for the admin to update | Roster owners update their own lists |
| Reports built by hand each month | Standard reports refresh automatically |
| Visitor follow up lives in inbox threads | Visitor record attaches to the household |
| Giving reconciled in a second tool | Giving sits on the same person record |
Common mistakes and how to avoid them
Three patterns derail otherwise solid migrations. The first is redesigning the data model mid-migration. Hold those improvements for month two. The second is leaving the spreadsheets live, which guarantees the team keeps two copies of the truth. The third is skipping the live walkthrough with each ministry leader, which is the single most reliable predictor of adoption.
What success looks like at day thirty
By the end of week four, three things should be true. The team performs the week's actual work in the new platform without falling back to the old sheets. Each ministry leader has updated their own roster at least once. Leadership has read one report from the new platform in a meeting and acted on it. If all three are true, the migration is complete. The remaining improvements are normal product work, not project work.