Multi-Campus Church Software

Multi-campus support is not available in Ekkli today. It's a genuine item on our roadmap — the underlying data model already has a place reserved for it — but there is no way for one Ekkli account to manage several linked campuses or locations yet. If you've seen multi-campus mentioned elsewhere as something Ekkli already does, that reference is wrong and this page is the correction.

What Ekkli looks like today: one church, one account

Right now, every Ekkli account is built around a single church: one login, one member database, one worship display, one giving setup, one dataset. That works well for a single congregation meeting in one place, but it doesn't fit a church running services across two or more locations under one banner — a second campus, a plant, or a satellite site that shares leadership, branding, or finances with the main congregation. Today, a church in that situation would need entirely separate Ekkli accounts per location, with no shared member records, no shared giving reporting, and no single login that sees across sites. That's a real limitation, not a small gap, and we'd rather say so plainly than let a feature page imply otherwise.

What "in development" actually means for this feature

Ekkli is built and run by a real team maintaining a live product, and we'd rather tell you plainly where a feature stands than let a marketing page get ahead of the code. For multi-campus specifically: the feature has a reserved place in our system's internal configuration, tied to our top plan tier and a "people" feature category — that's the kind of groundwork a team does when a feature is genuinely planned, not a guess or a placeholder page thrown up to rank for a keyword. But reserving a place in the data model is not the same as building the feature. Today, nothing in Ekkli lets one account manage several linked campuses, share a member base across locations, or roll up giving and attendance reporting site-by-site under one login. None of it exists yet.

We're not going to speculate about scope, screens, or a release window here. When multi-campus actually ships, this page will be rewritten to describe what it does, the same way our other feature pages describe real, working functionality.

What Ekkli already does today that's related

While true multi-campus management isn't built, several real parts of Ekkli are useful to a church already running more than one gathering:

• Member database. Ekkli's member management keeps a full admin-facing membership record for a single church account, including self-service join, invitations, and CSV import — a solid base for one location today, even though it doesn't yet span multiple linked accounts.
• Volunteer rota and scheduling. If a second service or venue needs its own rostered team, Ekkli's rota and volunteer scheduling, including confirm/decline/swap requests, already handles that within a single church account.

None of this adds up to true multi-campus management. It's the honest list of what's real and adjacent, so you can decide whether Ekkli is still useful to your church while you wait, rather than assuming a gap means the whole platform isn't ready.

What multi-campus churches can do with Ekkli today

Waiting for a feature to ship isn't always practical, so here's the workaround some multi-campus churches already use with Ekkli, stated plainly, trade-offs included: run a separate Ekkli account for each campus or location. Because Ekkli's six-month free trial covers a full church of up to 50 people with no card, this isn't a paid workaround — a main campus and a plant or satellite site can each run their own account at no cost, and each gets its own worship display, its own church website, and its own volunteer rota from day one.

For a lot of multi-campus churches, especially smaller ones or new plants, this is a genuinely workable setup, not just a stopgap to tolerate. If each location already runs its own Sunday service with its own volunteer team, preaches from its own worship display, and takes its own giving, separate accounts mirror how the campus already operates day-to-day. Campus pastors and local admins get full control of their own site without needing access to every other campus's data.

Be clear-eyed about what it costs you, though. Running parallel accounts means:

• No single login across campuses. A staff member who serves at more than one location — a worship leader who fills in at the plant, a regional pastor overseeing both — needs a separate login for each account and has to switch between them manually. There's no one dashboard that sees every campus at once.
• No unified member database. Someone who attends the main campus and later moves to the plant is two separate member records in two separate accounts, with nothing to link or migrate them automatically. If your church tracks a member's full history across locations, that has to be done by hand, outside Ekkli.
• No consolidated giving or attendance reporting. Each account reports on its own campus only. A combined view — total giving across all locations for the finance team, or attendance trends church-wide for leadership — means exporting from each account separately and totaling the numbers yourself, rather than pulling one report.
• No shared song library. Worship teams at each campus maintain their own copy of the song library inside their own account. If both campuses sing the same songs, someone has to add and update them in both places; there's no sync between accounts.

That's the real shape of the trade-off, and it's exactly the gap that a genuine multi-campus feature would eventually close: one login that spans every campus, a member base that's shared or at least linkable across locations and attendance reporting that rolls up church-wide while still breaking out by campus, and campus-level permissions so a local admin sees their own site without needing access to every other one. None of that exists in Ekkli today — the separate-accounts approach above is the honest, available alternative in the meantime, not a preview of the feature to come.

If your church needs centralized cross-campus reporting and single-login administration right now — not as a future roadmap item, but as a requirement today — dedicated multi-site church management software already exists and is worth evaluating. Products like FellowshipOne and TouchPoint are built specifically around managing multiple campuses under one system, and they've had years to mature that functionality. We'd rather point you toward software that actually does what you need today than have you wait on Ekkli for a feature that isn't ready. For churches whose campuses run fairly independently and where cost matters more than unified reporting, separate free Ekkli accounts per location are a reasonable way to operate until multi-campus is genuinely built here.

Everything else in Ekkli is ready today

Multi-campus being unbuilt doesn't mean the rest of the platform is unfinished. Worship display and remote control, the song library, sermon and teaching slides, your church website and member portal, sermon audio hosting, groups, event registration, and the member database are all live, working features on Ekkli's six-month free trial — no card required. See pricing for the full picture, or start using what's already built.

Tell us this matters to your church

If genuine multi-campus support would change whether your church can use Ekkli, tell us. We don't have a waitlist or signup mechanism specifically for this feature, but our contact page reaches the real team building the product, and genuine demand from churches with multiple locations is exactly what shapes what gets built next.

This page is maintained by the Ekkli team as an honest status update, not a sales page. It will be rewritten — with real detail and no guesses — once multi-campus is actually built.