Start Fresh
Getting Started
IntroductionStart a ChurchInitial SetupChurch ProfileCampusesLogoModulesSystem ConfigurationUsers & Roles
OverviewCreating UsersRole MatrixFlock Leader ScopesCustom FieldsConnect CardFirst-Time VisitorsPrivacy RequestsFinance Settings
OverviewFundsFiscal YearOnline Giving SetupStatement ConfigPayment MethodsBank AccountsSecurity
OverviewActivity Log
Activity LogStart Fresh
Start FreshStart Fresh
Start Fresh deletes records so your church can begin again, for the whole church or for one campus. Use it to clear test data or a practice import before you go live, or to redo one campus's setup. Nothing can be undone. Before anything is deleted a backup is written, and it is the only record.
Getting Here
Navigation: Settings → System → Start Fresh
Who Can Use It
- Super Admin only. No other role is offered the page, and the reset itself is refused for anyone else.
- Two-step verification is required. A Super Admin without it is told to turn it on first, because confirming asks for a code from the authenticator app.
- Not on the demo church, which keeps itself current: its dates move forward a week at a time.
- SanctuaryOS support can run the same reset for a church from its own console, with its own two-step code. The church's Activity Log records it as the support person's name followed by “(SanctuaryOS support)”.
1. Where
Choose The whole church or one campus only. A campus reset deletes only that campus's records in the parts you tick: a gift belongs to the campus of its session, and attendance to the campus where it was recorded. Rows recorded at another campus that belong to this campus's people or services go with them, and the preview lists them; a kept session that loses such a gift has its totals worked out again. People with no campus are removed only by a whole-church reset.
2. What to Reset
Tick the parts to reset:
| Field | Type | Description |
|---|---|---|
| Flock | Module | People, households, notes, child profiles, onboarding progress and engagement scores. |
| Steward | Module | Gifts and sessions, deposits, pledges, recurring gifts, giving statements and giving imports. |
| Gather | Module | Services and their attendance, check-ins and pickups, orders of service, headcounts and absence alerts. Service schedules are kept, so upcoming services are created again from them. |
| Serve | Module | Schedules and slots, team rosters, blackouts, volunteer requests, burnout alerts and setlists. Teams are kept. |
| Serve setup | Extra | The serve teams themselves and their roles. |
| Circles | Module | Memberships, meetings and their attendance, prayer requests and join requests. Groups are kept. |
| Circle groups | Extra | The circle groups themselves. |
| Care | Module | Care items, notes, visits, follow-ups, bereavement reminders and milestones. |
A part that other records depend on brings them along, so a reset never leaves half a module. Ticking it ticks the dependent parts, marked Added automatically, and says why:
- Flock also resets Steward, Gather, Serve, Circles and Care, because gifts, receipts, attendance, rosters and care items all point at people.
- Gather also resets Serve (schedules point at services).
- Serve setup also resets Serve.
- Circle groups also resets Circles.
3. Preview
Preview what will be deleted counts everything and deletes nothing. The preview shows:
- one sentence stating the scope, for example “This will delete 97 people and everything attached to them at Montreal”
- the exact number of rows per kind of record, and the total
- Across campuses: rows recorded at another campus that go with this campus's people or services; households kept because they have members on another campus (only this campus's people leave them); and people with no campus
- Logins linked to people being deleted: they keep their login and roles, and their link to a person is cleared until someone links them again
- kept records that have a link cleared
- what is still there afterwards (see below)
What Blocks a Reset
Some records must never be deleted. When any of these is in scope, Steward and Flock cannot be reset:
- any CRA receipt, live or void
- a gift on a CRA receipt
- real money through Stripe: an online gift or a refund
The blocked parts are unticked by themselves and the rest is previewed, with the reason and what can still be reset, for example “You issued 1 CRA receipt for 2026 at this campus … You can still reset Gather, Serve, Serve setup, Circles, Circle groups and Care.” When online giving is in Stripe test mode, online gifts are test money and do not block; the page says so.
4. Confirm
Click Continue to confirm. The Delete for good? dialog asks for:
The church name (or, for a campus reset, the campus name), typed out. Capitals, spacing and the kind of dash do not matter.
A fresh 6-digit code from your authenticator app.
For a church with a paid subscription, a tick on "I understand this church is live and has a paid subscription, and that what I am deleting cannot be brought back." The page also shows a stronger warning for a paying church.
A 10-second countdown on the Start Fresh button before it can be clicked.
The confirmation must come from the Super Admin who ran the preview, within 30 minutes of it, and the counts must not have changed since. Otherwise run the preview again.
While It Runs
- A banner on every page, for everyone in the church, reads “Start Fresh in progress, changes are paused”. People can still sign in and look around; saving works again when it finishes.
- Scheduled background jobs for the church are skipped until it finishes.
- The Start Fresh page shows progress: writing the backup, deleting each part, then recalculating engagement, circle health and serve stats.
- Only one reset can run for a church at a time.
- Until it starts deleting, a Super Admin can Cancel this reset from the banner or the Start Fresh page. Nothing has been deleted, and changes work again at once. Once it is running it cannot be cancelled.
- A reset that never starts does not keep the church paused: if it has been waiting 10 minutes with nothing working on it, or an hour in any case, it is marked failed, nothing is deleted, changes work again, and the page says so.
Each part is deleted as one step, so a part is either fully reset or untouched. If a run stops, the parts that finished stay reset, nothing is half-deleted, changes are no longer paused, and the page says why it stopped. Preview again to reset what is left.
Afterwards
- The page says it finished, how many rows were deleted, and what is still there.
- Super Admins and the Lead Pastor are emailed, with a link to the Start Fresh page.
- The reset is one Start Fresh entry in the Activity Log, and its alert fires (by default to every Super Admin).
- After a Flock, Steward or Gather reset, the First-Time Setup guide is back in the header.
- Upcoming services are created again from the kept service schedules within the hour.
Reset History and the Backup
Reset history lists each reset: when, where, which parts, who ran it, the number of rows deleted, and the reason a stopped run stopped. Each has Download backup: a ZIP of spreadsheets holding every deleted row, plus unlinked.csv with the previous value of every link that was cleared. A backup is kept for 30 days, then deleted by the nightly start-fresh-purge job, and the history says so. Downloading a backup is recorded in the Activity Log as an export.
What Is Never Touched
- users and their logins (a link to a deleted person is cleared)
- roles and campuses
- funds and bank accounts
- lookup tables and custom field definitions
- children's rooms and Order of Service templates
- service schedules
- email templates and giving pages
- the song library
- integrations, including the Stripe connection
- billing and your plan
- the Activity Log
- receipt and deposit numbering (numbers are never reused)