Enterprise DNA

Instead of Planning Center

Stop renting Planning Center. Own your service-planning system.

We build your version around your services, teams and safeguarding policies, map your Planning Center exports, and run it for you through Omni by Enterprise DNA.

Planning Center People is free, and Services is free for five team members. Paid Services capacity grows with your team; Music Stand adds US$5 a month. Compare your actual subscriptions before switching.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

Compare your current bill

Start with the products your church actually uses

Planning Center prices products separately. A free people database is already included. Check the paid capacity and supporting tools your teams rely on.

people

A free people database

Planning Center People already includes unlimited records and reporting for free. Owning your operating rules is the reason to consider a change.

groups

Services grows with the team

Services starts with a free tier for five team members. Paid capacity is based on the number of team members.

music_note

Music Stand is an add-on

The pricing page lists Music Stand at US$5 a month. Keep rehearsal software in your comparison if musicians depend on it.

event

Facilities have their own measure

Calendar includes unlimited events; room management determines its paid capacity. Review that separately from service planning.

check_circle

Attendance has its own product

Check-Ins uses Sunday check-in counts for its plan measure. Agree the children’s ministry workflow before changing systems.

forum

Groups are another capacity choice

Groups plans use the number of people in groups. Compare the products you actually use against a version built for your church.

What your version does

Run the weekly service desk from records you own

Sunday readiness

See the missing people before the service

Required roles, accepted replies and pending requests are counted together.

  • check Confirmed gaps by role and service
  • check Outstanding replies with names and dates
  • check Separate campus coverage totals
  • check Children volunteer roles with unfilled places

Volunteer care

Put the rota beside the follow-up

Workload and overdue tasks can be read together from the same records.

  • check Assignments across the next four weeks
  • check Overdue follow-ups beside upcoming commitments
  • check Blocked dates checked before assignment
  • check Overlapping assignments rejected

Worship planning

Keep the running order and song history together

Build the service sheet from the same plan the coordinator reviews.

  • check Ordered items with durations and musical keys
  • check Time remaining within each planned service
  • check Completed and upcoming song uses
  • check Missing or expired music-permission evidence flagged

Your records

Keep a record you can change

Your church decides its fields, review dates and reports.

  • check One-step import of exported people
  • check Screening evidence checked for teams that require it
  • check Privacy review dates and append-only notes
  • check Service sheets, team rosters and follow-up drafts in your brand

Make it yours

Design your own Planning Center replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Planning Center. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Planning Center replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Planning Center data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Church Services for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Church Services for Claude Code

Connected to your own database

Which upcoming roles still need confirmed people?

SUN

Arts_at te
2026-10-11T09:00:00.000Z
Am ro
Children volunteers
Le ne
Room helper
Eded ac
2
Cepted pe
1
Nding ga
0
P
1

SUN

Arts_at te
2026-10-11T09:00:00.000Z
Am ro
Welcome
Le ne
Door host
Eded ac
2
Cepted pe
0
Nding ga
1
P
2

EVE

Arts_at te
2026-10-11T18:00:00.000Z
Am ro
Music
Le ne
Keys
Eded ac
1
Cepted pe
0
Nding ga
1
P
1

NEXT

Arts_at te
2026-10-18T09:00:00.000Z
Am ro
Music
Le ne
Keys
Eded ac
1
Cepted pe
0
Nding ga
1
P
1

Ask it anything

Questions your service coordinator can answer today

These questions run against the fictional demo records. They show the working queries in the free version, without claiming that Planning Center lacks comparable reports.

chat_bubble Which upcoming roles still lack confirmed people?
chat_bubble Who has not replied to an upcoming assignment?
chat_bubble Who has overdue follow-ups and upcoming assignments?
chat_bubble Which child-facing roles still need confirmed volunteers?
chat_bubble Which planned songs need their permission evidence reviewed?
chat_bubble Who has the heaviest roster over the next four weeks?
chat_bubble How much of each service remains unallocated?
chat_bubble Which campuses have the largest confirmed-person gaps?
chat_bubble Which assignments now conflict with a blockout or screening review?
chat_bubble How often have songs been used, and what is planned next?

Switching

How to switch from Planning Center

The move involves exporting people, mapping the records and rules you need, testing the import, and checking the results before you stop using Planning Center.

  1. 1

    Export people and records

    Start with the people records you want to bring across. Export them in whatever format your Planning Center account allows, usually CSV or Excel, and check with Planning Center if you are unsure how to export. Keep the existing IDs, names and email addresses in the export. List the service plans, team memberships, songs, messages and other history you may also want to move, since those need separate mapping.

  2. 2

    Test the people import

    Load a copy of the people export into the new database, starting with the import’s test run rather than applying the changes immediately. The import uses existing IDs, names and email addresses, and supports repeat imports. Review the test result before proceeding. This lets you catch issues with the people data before you rely on it for service planning.

  3. 3

    Review issues and map history

    Check the import results for validation issues or ambiguous records, then resolve them before relying on the imported data. People import does not move a complete Planning Center account. Team membership, songs, service plans, check-in history, giving and messages require separate mapping. Decide which records and history matter to your operation, and confirm how each selected item will be reconciled.

  4. 4

    Run both side by side

    Keep Planning Center in use for a short period while you check the new database against your current records and workflows. Compare the imported people and any separately mapped service plans, team memberships or other history. Ask coordinators to verify that the records they need are present and correct. Keep track of differences and resolve them before making the new system your operating record.

  5. 5

    Switch off Planning Center

    Stop using Planning Center for the records you have checked only after the side-by-side review is complete and the new system has the information you need. Make clear to staff when to stop updating the old account, so records do not diverge during the change. Keep any records you have not migrated available according to your church’s own retention and access requirements.

construction

Where the real effort goes

The main work is usually deciding how your own fields and operating rules map, then choosing how much history to bring. People can be imported, but service plans, team membership, songs, messages and other history need separate mapping and reconciliation. When you have Enterprise DNA install and run it, they handle the agreed migration work with you.

Not ready for a call?

Get your Planning Center switch plan by email

We will send you the step-by-step plan for moving your business off Planning Center, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose who builds and runs your version

Open source

Do it yourself

Free code. Your hosting and agent costs.

  1. 1 Clone the repo and install its dependencies
  2. 2 Run npm run demo and inspect the fictional records
  3. 3 Use Claude Code, Codex, OpenCode or Cursor with the included commands
  4. 4 Read the switch guide and test your Planning Center people CSV import
Get it on GitHub

Built around your business

We customise it

One setup fee, then an agreed retainer

  • check Your service formats, campus fields and screening policies
  • check Your Planning Center exports mapped and reconciled
  • check A web front end or different technology where your church needs it
  • check Your agreed connections and document layouts built and tested
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Migration reconciled with your original records
  • check Staff access, backups and agreed connections configured
  • check Your weekly planning and review routine maintained
Talk to Sam

Questions

Instead of Planning Center, answered

Why change if Planning Center People is already free? expand_more

The case is ownership and a fit with your church’s way of working. People already includes a free database and reporting. Compare the paid products you use and the changes you need before deciding to move. There is no blanket savings promise.

What comes across from our Planning Center account? expand_more

The free version imports exported people using their existing IDs, names and email addresses. It offers a test run and repeat imports. Service plans, team membership, songs, messages and other history need separate mapping. Enterprise DNA agrees that scope and reconciles the results with you.

Can our volunteers still use phones and rehearse together? expand_more

Tell us which phone, notification and rehearsal workflows your teams depend on. Enterprise DNA scopes suitable screens and connections for your version, then tests them with your coordinators and volunteers before you change over.

Does this cover children’s check-in and safeguarding? expand_more

It checks recorded screening evidence before assigning someone to a team that requires it. Your safeguarding lead sets and validates the policy. Child check-in, guardian authority and pickup verification require a separately designed and validated workflow. A clear evidence report is not certification.

Who looks after the system and what does it cost? expand_more

The code is free to run yourself, with your own hosting and agent costs. Enterprise DNA can customise and operate it for one setup fee followed by a retainer. The agreed work covers migration, access, backups and the connections your church needs.

Bring your service plan and your current bill

Spend 30 minutes with Sam reviewing the work your church needs done, the Planning Center products you use and what your own version would involve. Agree the migration and operating scope before committing.

Book a call with Sam Get the free version

Church Services for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Planning Center?

Get your version built