Why firms delay moving systems
Most independent funeral firms do not stay with an old process because they like it. They stay because the idea of moving live cases, family contact details, invoices and documents sounds risky. That is a reasonable concern: if a move is rushed or poorly scoped, the new system can create more work at precisely the wrong time.
The alternative is not an all-or-nothing migration. A good plan begins with the work that is current and creates a safe, reviewable path for anything historic.
Start with the information that matters now
For most practices, the first migration should focus on active operational records. That normally means:
Open cases
Deceased and family contact details, arrangements, service dates, special requirements, notes and current documents.
Outstanding work
Tasks, approvals, supplier actions, unrecorded disbursements and invoices that have not yet been paid.
Current reference data
Suppliers, staff users, locations, standard services and any working templates the team relies on day to day.
Historic cases can then be exported for retention and brought across later only if there is a genuine operational reason. Carrying every duplicate or outdated record into a new system usually adds cost and confusion without helping the team.
A practical migration sequence
- Export before changing anything. Take a complete, readable export from the current system and confirm who is responsible for keeping it securely.
- Decide the minimum safe first move. Identify open cases, current invoices, upcoming services and active supplier details.
- Clean and map the data. Remove obvious duplicates, agree the format for dates and names, and identify which existing columns map to which new fields.
- Test with a small set. Import a representative sample and ask the people who do the work to verify it—not just the person leading the project.
- Train around real scenarios. Create a case, assign a task, record a disbursement, create a family communication and produce an invoice.
- Switch in a controlled way. Begin using the new system for agreed cases or from an agreed date, retaining read-only access to historical records for an appropriate transition period.
Do not make migration a test of loyalty. The new system needs to be good enough that staff will use it in the middle of a busy day. If it cannot manage a live-case scenario more clearly than the old approach, pause and fix the workflow before rolling it out.
Data protection and continuity
Funeral practices handle sensitive personal information. Before a migration, identify the data controller, confirm the supplier’s data-processing arrangements, limit access to those who need it, and keep exports in an appropriate secure location. This is operational guidance, not legal advice; firms should obtain specialist advice where their circumstances require it.
Continuity for families is the most important measure of success. The team should always know which system contains the current case record during the transition. Avoid parallel working for longer than necessary, because it makes conflicting records more likely.
How Hallowed supports a staged move
Hallowed is designed to give independent firms a structured way to build their working case records, users, suppliers, templates and active workflow. The sensible first step is to set up the practice, test the core journey with non-sensitive sample data, and then move active cases in a planned sequence.
You retain ownership of your data. Hallowed provides data export tools so a firm can keep a portable record and should not be locked in merely because moving elsewhere feels difficult.
Questions funeral directors commonly ask
What data should move first?
Prioritise open cases, family contacts, service details, active tasks, current documents, outstanding invoices and current suppliers. Historical records can be assessed separately.
How long does migration take?
It depends on the condition and volume of existing data, but a staged approach usually reduces disruption. The time to clean and validate data is more important than the time to import it.
Will staff need a lot of training?
They should be trained on the few real workflows they repeat every day. Short, scenario-based training is generally more useful than a long feature tour.