Switching
How to Switch Celebrant Practice-Management Software (Without Losing a Single Client Record)
What stops most celebrants switching isn't doubt that a better tool exists. It's the fear of losing a client record somewhere in the move.
Facts last verified 24 July 2026. Sources listed in full below.
On this page
- Quick answer: the short version
- Why celebrants put off switching
- Before you switch: a pre-migration checklist
- The switch, step by step
- What switching actually costs you (vs what staying costs you)
- Switching from a specific tool
- Common switching mistakes celebrants make
- How CelebrantCentral makes switching easier
- Frequently asked questions
You've probably had this thought at least once this season: the software you're using wasn't built for you. Maybe it's a spreadsheet that's grown legs. Maybe it's a photography CRM that's never heard of a Notice of Intended Marriage. Whatever it is, the tool has stopped fitting the job, and you know it.
What actually stops most celebrants from switching isn't doubt that a better tool exists. It's the switch itself — the fear of losing a client record, a signed document, or a ceremony date somewhere in the move. That fear is reasonable. You've married a hundred couples; you know exactly what it costs when paperwork goes missing. This guide is the answer to that fear: a step-by-step way to move your business to new software without losing anything that matters.
Quick answer: the short version
Switching celebrant software safely comes down to five steps:
- Export everything from your current tool — client list, ceremony dates, notes, and documents — before you touch anything else.
- Check your record-keeping obligations. Some client records have to survive the move by law, not just by convenience.
- Import into the new platform and check it against your original export, line by line.
- Deal with in-flight ceremonies first — anything with a live Notice of Intended Marriage countdown running gets moved and checked before anything else.
- Run the new system alongside the old one for one full ceremony cycle before you cancel anything.
Done properly, switching takes a few real hours spread across a week or two — not a lost weekend, and not a lost client record.
Why celebrants put off switching
In our own survey of 234 Australian celebrants, one respondent — a celebrant doing around 50 weddings a year — put the hesitation better than we could:
"It took me ages to set up my Dubsado! Knowing I would have to go through that process again and get to know a new systems puts me off using a new one, but I'd do it if it was truly going to be a better platform for me."
That's the most honest sentence in the whole dataset. Not "I don't need to switch" — "I'd do it if it was truly going to be a better platform." The hesitation isn't about whether a better tool exists. It's about the risk of the move itself.
That's a fair thing to be careful about. You've built your business around a system that, however clunky, currently works. Every client record, every note about a nervous couple, every ceremony script sits inside it. Ripping that out and hoping it lands somewhere else feels like exactly the kind of risk a careful, detail-oriented celebrant should be wary of — because you are one, and paperwork mistakes have consequences you can't undo after the fact.
Here's the part that actually defuses it: the risk in switching software was never the switch. It's switching badly — cancelling the old system before you've confirmed the new one has everything, or moving everything at once in the middle of your busiest month. Handled step by step, with your data exported and checked before you cancel anything, switching is boring in the best way. Below is exactly how.
Before you switch: a pre-migration checklist
Export what you have
Before you sign up to anything new, get a full export of what you already have — while you still have full access to your current tool. At minimum:
- Your client/couple list — names, contact details, ceremony dates
- Ceremony notes — anything about the couple's story, requests, vow drafts
- Documents — signed contracts, questionnaires, Notice of Intended Marriage paperwork, Form 15 records
- Payment/invoice history — for your own records and for tax time
Most tools let you export a CSV of your client list from a settings or reports menu. Documents and notes are less standardised — some tools bundle everything into one export, others make you download file by file. Confirmed 24 July 2026 against each vendor's own help centre: Studio Ninja and HoneyBook export contact/client details only as CSV (documents aren't included); Dubsado exports a customisable CSV of client and project data with custom-mapped fields; 17hats exports contact details as CSV but says plainly that "project information including documents, project details, emails, time logs, etc. will need to be saved individually." Either way, do this before you cancel anything and before your subscription lapses. Once access closes, so does your export.
Know your record-keeping obligations that carry over
Switching your software doesn't switch your legal obligations. As a marriage celebrant, you're required to keep certain records for a set period after the ceremony, including Notice of Intended Marriage documentation and your Form 15 records — a legal requirement under the Marriage Regulations 2017 (Cth), reg 73(5), and one that must be kept for 6 years (reg 73(6)). Worth noting before you export: that's six years of completed ceremonies, not just the ones still active. That obligation exists whether your files live in Dubsado, a spreadsheet, or a purpose-built celebrant platform — it doesn't move on its own just because you do.
Before you switch, know exactly which records you're required to keep, for how long, and make sure your export includes them — not just live ceremony data, but archived records from ceremonies you've already completed. (For the full state-by-state detail on Notice of Intended Marriage requirements, see our Notice of Intended Marriage guide.)
Time your switch
The worst time to switch software is the week before a wedding with an active Notice of Intended Marriage countdown running. Pick a quiet stretch — between ceremony seasons, or a run of a few weeks with nothing booked — and do the move then. If your calendar genuinely has no quiet stretch, that's what the parallel-run step below is for. You don't have to choose between switching and protecting an in-flight ceremony.
The switch, step by step
Step 1: export your data from your current tool
Start here, always. Log in to your current tool and pull everything — client records, ceremony dates and notes, documents, invoices. Save it somewhere outside that tool: a folder on your own computer or cloud drive, not a screenshot. Each tool's export lives in a different place — a dedicated "Export clients" tool in Studio Ninja, a customisable CSV export from the Projects tab in Dubsado, a contacts download from the Clients page in HoneyBook, a CSV export from the Contacts or Leads page in 17hats — so don't assume a single method carries across vendors; check your specific tool's own help centre before you start. If your current tool doesn't offer a clean export, at minimum copy the essentials manually before you commit to a new system — client names, ceremony dates, and anything with a legal deadline attached.
Step 2: import into the new platform
Bring your export into the new tool. Most celebrant and CRM platforms accept a CSV import for client and ceremony records; documents usually need to be attached individually once your ceremony records exist. Set aside a proper block of time for this rather than doing it in five-minute gaps — half-finished imports are where records go missing.
Step 3: reconcile in-flight ceremonies first
Before anything else, check every ceremony with a live Notice of Intended Marriage clock running. Confirm the date, the couple's details, and the paperwork status match exactly between old and new systems. These are the records you genuinely can't afford to get wrong — everything else can be tidied up over the following week.
Step 4: run parallel for one ceremony cycle
Don't cancel your old subscription the day you finish importing. Run both systems side by side for one full cycle — through at least one upcoming ceremony, ideally a full season if your volume allows it. Use the new tool for real work, and keep the old one open as a safety net you can check against.
Step 5: cancel the old subscription only after the parallel run confirms
Once you've been through a live ceremony (or several) on the new system without incident, cancel the old one — not before. This is the step most celebrants skip when they're keen to be done with the move, and it's the one that actually protects you if something didn't transfer cleanly.
What switching actually costs you (vs what staying costs you)
Switching software costs you a few real hours: exporting, importing, checking, running parallel. Spread over a couple of weeks, that's manageable alongside a normal ceremony calendar.
Staying on a mismatched tool costs you differently — in small, repeated amounts that never show up as a single bad afternoon. It's the double entry every time a booking moves from enquiry to confirmed. It's manually copying a couple's details into a separate Notice of Intended Marriage document because your CRM has never heard of one. One respondent, in our earlier 114-celebrant deep-dive survey, put the actual cost of this plainly (n=114):
"Unless the software could send the completed documents and details directly to the BDM, I would still have to double enter everything."
Multiply that by every ceremony, every season, and the admin time adds up — not as one bad afternoon, but as a recurring tax on every ceremony you run for as long as you stay on a mismatched tool.
The honest comparison isn't "switching is free." It's a few hours once, against an ongoing tax on every single ceremony you run afterwards.
Switching from a specific tool
What actually transfers cleanly, and what needs a second look, depends on what you're switching from.
| Coming from | What transfers easily | What doesn't | Double-check this one thing |
|---|---|---|---|
| Studio Ninja | Client contact details, booking dates, basic notes | Anything built around a photography workflow — shoot schedules, gallery links, image-delivery steps — there's no celebrant-side equivalent to move it into | Studio Ninja's client export (Dashboard > Clients > Export clients) is a fixed CSV of contact details, lead/job counts, consent records and notes — it doesn't bundle documents or contracts, so pull those separately (confirmed via Studio Ninja's help centre, 24 July 2026) |
| Spreadsheets & Google Drive | Everything, technically — it's already yours, in a format you control | Structure. A spreadsheet has no enforced fields, so imports land messy unless column headers are cleaned up first | Every ceremony with a Notice of Intended Marriage in progress has a clearly dated row before you import — a missed date is the one mistake worth catching |
| A generic freelancer CRM (17hats, HoneyBook, Dubsado) | Client contacts, basic booking/invoice history | Legal or celebrant-specific fields — Notice of Intended Marriage status, Form 15 records — because these tools were never built to hold them | Confirmed 24 July 2026: HoneyBook and 17hats export contact details only as CSV — no documents, and 17hats says outright that project documents "need to be saved individually." Dubsado's CSV export is more configurable (client + project fields, incl. custom-mapped fields) but still doesn't bundle attached files — check each tool's own export before assuming documents come with it |
| Another celebrant tool (Celebrant Easy, Celebrant Briefcase, Byronware/Celebrant Suite) | Thinner than the mainstream CRMs above. The underlying data model is closer to yours, but none of the three publishes a data-export help page as at July 2026 | Celebrant Easy's own FAQ says your data is completely removed once your subscription's cancellation finalises, with no guaranteed retrieval afterwards — so get everything out before you cancel, not after. Celebrant Briefcase's model keeps your weddings viewable and your forms regenerable inside their system even without a current licence, rather than offering a download. Byronware/Celebrant Suite has an in-app Report Centre, a way to transfer a wedding between two Byronware users (an internal transfer, not an export), and an automated local backup on the desktop edition — but nothing published on moving your data to a different platform | Ask the vendor directly, in writing, before you commit to a switch date. There's no published export documentation to check against, so don't assume a CSV — or a locked PDF, or anything at all — will be waiting for you (all three checked 25 July 2026) |
Scroll the table sideways →
Common switching mistakes celebrants make
- Cancelling the old subscription before confirming the new one has everything — the single most costly mistake, and the easiest to avoid (see Step 5, above).
- Switching mid-season, with active Notice of Intended Marriage countdowns in flight, instead of picking a quiet window.
- Only exporting the client list and forgetting documents — signed contracts, questionnaires, Notice of Intended Marriage paperwork — which are often stored separately from contact records.
- Assuming everything imports automatically. Most platforms import contact and booking data cleanly; documents and notes usually need a manual pass.
- Not checking record-keeping obligations before archiving old data — deleting a completed ceremony's files because "it's done," when a retention period is still running.
How CelebrantCentral makes switching easier
For what it's worth, everything above is the process we'd want any celebrant to follow, regardless of what they switch to. If you do land on CelebrantCentral, the destination is a single home for leads, bookings, Notice of Intended Marriage and Form 15 handling with BDM prefill, your couple portal, invoicing, GST, and payments — the parts of the job that currently live in five different tools.
It's priced at $2 + GST/month per active ceremony, capped at $40 + GST/month, hard — leads stay free until they're booked, and there's no lock-in. CelebrantCentral was co-founded by Luke Firth, a working Australian marriage celebrant and ABIA Australia's Best Celebrant 2025, who ran into every one of the problems above himself — the tool exists because he needed it to.
Founding Celebrant
Be first in line. CelebrantCentral launches 1 October 2026. Founding Celebrant places are capped at 100, with pricing locked for life plus the badge. Join the notify-me list to hear the moment they open.
One email when places open, plus the occasional guide. Confirm your address to join — unsubscribe any time.
Not sure switching is even worth it yet? Read our honest spreadsheets vs CRM comparison first — it might tell you to stay exactly where you are.
Frequently asked questions
How do I switch from Studio Ninja to a celebrant-specific CRM?
Export your client and booking data from Studio Ninja, then import it into the new platform and check it record by record. Studio Ninja is built for photographers, so anything celebrant-specific — Notice of Intended Marriage status, Form 15 records — won't be in there to move; you'll set those up fresh in the new system. Studio Ninja's own export tool (Clients tab > Export clients) gives you a CSV of contact details, notes and job counts, but not documents — those come out separately (confirmed 24 July 2026).
Will I lose my client data if I switch celebrant software?
Not if you follow the export-first sequence: pull a full export before you touch the new tool, import and check it against the original, reconcile any in-flight ceremonies, then run both systems in parallel for one ceremony cycle before cancelling the old one. Data loss happens when celebrants skip the export step or cancel the old tool too early — not because switching itself is risky.
What's the safest way to migrate from spreadsheets to a CRM as a celebrant?
Clean up your spreadsheet first — consistent column headers, one row per ceremony — then import it as a CSV. Because a spreadsheet has no enforced structure, the main risk is messy data landing in the wrong fields, so check every ceremony with an active Notice of Intended Marriage date especially closely after import.
How long does it take to switch celebrant business software?
The active work — exporting, importing, checking — is typically a few hours spread across a week or two, not one big session. Add a full ceremony cycle of running the old and new systems in parallel before you cancel anything, so the whole process from start to fully switched over usually spans a few weeks.
What should I check before switching celebrant CRM providers?
Confirm the new platform actually handles what your current one doesn't — Notice of Intended Marriage and Form 15 handling, in particular, if you're a marriage celebrant. Check what a full data export from your current tool actually looks like before you commit to anything. And check your own record-keeping obligations for completed ceremonies, so nothing gets archived or deleted before its retention period is up.
Sources & further reading (5)
- CelebrantCentral survey of 234 Australian marriage celebrants, 2026 (objection data §6, verbatim quotes)
- Marriage Regulations 2017 (Cth), reg 73(5) record contents and reg 73(6) six-year retention — www.legislation.gov.au/F2017L01359/latest/text — Compilation No. 3 (14 October 2024), re-confirmed 25 July 2026
- Studio Ninja, 17hats, HoneyBook, Dubsado — current data-export/help-centre documentation, VERIFIED 2026-07-24: help.studioninja.co/en/articles/4148304-how-to-export-client-list · help.17hats.com/en/articles/843725-how-do-i-export-my-contact-list · help.honeybook.com/en/articles/2650752-download-and-export-your-contacts-list-from-honeybook · help.dubsado.com/en/articles/2779503-export-data-from-dubsado (full detail in)
- Celebrant Easy, Celebrant Briefcase, Byronware/Celebrant Suite — each vendor's own published pages, checked 25 July 2026: none publishes data-export documentation. www.celebranteasy.com/faqs · celebrantbriefcase.com.au/ · byronware.com/faq/ · byronware.com/whats-new/
- CelebrantCentral product brief (pricing, feature, and launch-date claims)