Changing Funeral Software or CRM Providers: Records, Migration and Exit Questions
Before changing funeral software or CRM providers, establish what your team will still be able to find, understand and use after the move. A promise to import contacts does not settle whether family relationships, documents, contact preferences, outstanding enquiries or historical arrangements will remain usable. An accounting export answers a different question from a complete exit agreement.
This guide is for funeral-home owners and operations managers comparing a proposed move. It helps you judge the written scope, the work your staff must approve and the obligations that continue when a subscription ends. The aim is a purchasing decision you can defend, with clear exceptions and costs, rather than an assumption that everything transfers. Your licensed operator retains responsibility for family care, professional decisions and required records.
Decide what is actually changing
A new CRM, a replacement funeral management system and a new website can involve different records, suppliers and responsibilities. Decide which purchase solves your problem before asking for a migration price.
- Keeping funeral management software and adding enquiry support: the new service may need only permitted enquiry information, contact preferences and staff responsibilities. Detailed arrangement, contract and financial records may remain in the existing system.
- Replacing the operational platform: the scope may involve active cases, historical arrangements, documents and other records your operator must continue to access. Each category needs its own inclusion or exclusion decision.
- Changing the website supplier: obituary pages, public links, media rights and contact routes need attention even if your internal software stays the same.
If a proposal treats all three as one undifferentiated “data migration,” ask the supplier to separate them. You need to know which organisation holds the source information, which recipient can receive it and who is responsible for each dependency. Keeping a suitable existing system can be a reasonable outcome; a CRM engagement does not automatically require replacing it.
Agree the records and context your team needs
“All customer data” is too vague for a funeral business. A person may appear as an enquirer, a family contact, a pre-planning client or an authorised representative. Those relationships and their purposes matter. Copying a name and telephone number alone may leave staff unable to tell what the person asked for or whether further contact is appropriate.
Use the proposal to distinguish information needed in the new service from information that should remain in an approved record system or archive. The table below is a buying aid, not an instruction to transfer every category.
| Information category | Decision to settle in the scope | What an incomplete promise misses |
|---|---|---|
| Open at-need enquiries | Which permitted enquiry details and staff responsibilities must remain available? | A contact list does not show who is handling an unresolved request. |
| Voluntary pre-planning enquiries | Will the reason for contact, agreed next step and current preferences remain understandable? | An enquiry is not evidence of a prepaid arrangement or permission for every later message. |
| Contracts and prepaid arrangements | Which approved system retains the authoritative agreement and associated records? | A CRM label or copied summary is not a substitute for the underlying contract or regulated records. |
| Historical cases and attachments | Which history and documents are included, retained elsewhere or unavailable? | A list of completed cases may exclude documents, relationships and the context of earlier decisions. |
| Obituaries, photographs and public links | What must remain public, what rights apply and which supplier controls it? | A media file alone may not preserve its publication permission, page address or correction history. |
We assess your existing tools and scope enquiry management, approved communications and staff handover.
For each included category, the agreement should say what “available” means. Searchable access for authorised staff, a readable archive and a working connection to another supplier are different deliverables. Have your operator and relevant advisers determine the legal recordkeeping requirements; do not let a convenient software category make that decision.
Ask for evidence of a usable export
The right to receive a file and the ability to use its contents are separate questions. A spreadsheet might provide financial totals while omitting correspondence and supporting documents. A collection of PDFs might be readable but leave staff unable to tell which documents belong together. Neither is necessarily unsuitable, but neither proves that the proposed replacement can support your required work.
Before committing, ask each supplier to explain the information it can release or receive, the format, the included history and the important exclusions. Request a demonstration using synthetic records or another specifically approved, privacy-appropriate example. Do not send family files through a general sales form to obtain a quote.
A useful demonstration answers a business question: can an authorised member of your team identify the relevant enquiry, understand its current position and find the supporting information included in the scope? It should also make missing information visible. A successful opening of one file does not establish that every record, attachment or historical period is covered.
Clarify whether an export requires an active subscription, supplier assistance or a separate fee. Ask what access remains after cancellation and whether a later correction or access request can still be handled. These answers belong in the agreement, rather than in a salesperson’s general assurance that “you own your data.”
Keep permissions and privacy decisions attached to the move
Changing software does not, by itself, create a new right to contact a family or use its information for another purpose. An individual who requested a planning conversation has not necessarily agreed to recurring promotional messages. A request to stop contact must not disappear because the old system held that preference separately.
The Office of the Privacy Commissioner of Canada’s meaningful-consent guidance explains why sensitivity, purpose and people’s reasonable expectations matter. Confirm the applicable federal and provincial requirements with your privacy adviser. Information about deceased people and sensitive information about living family members should not be treated as one uniform legal category.
A transfer for an already authorised purpose needs a different assessment from adding advertising, profiling or a new communication purpose. Confirm whether the proposed recipient or purpose changes the permission required; earlier permission does not necessarily cover a new use. Resolve who may receive the information, why they need it and what restrictions remain before including the transfer in the engagement.
The OPC’s cloud guidance for businesses also makes clear that outsourcing does not remove an organisation’s accountability. Ask about supplier access, subcontractors, storage and processing locations, incident responsibilities and exit arrangements. A Canadian address or a security badge alone cannot answer those questions. Your assessment must reflect the information involved and the laws that apply to your operation.
Separate historical coverage from ongoing connections
A connection between two systems may support new activity without carrying earlier history. It may cover some record types and stop updating others after a particular status change. A website connection may publish selected information while the operational system remains responsible for later corrections. “Integrated” does not identify these boundaries.
Ask the suppliers to name the authoritative system for the information that matters to your team. The proposal should explain which direction agreed updates travel, which historical records are included and what exceptions require staff attention. These details define the service and limitations your team is being asked to approve.
For example, if a planning enquiry becomes a documented arrangement, ask whether its earlier conversation remains accessible and where staff should look for the current position. If a public obituary is corrected, ask which supplier is responsible for keeping the intended public version accurate. The important purchasing question is whether the agreed service preserves the context your staff need, with limitations they can recognise.
Name who carries the work through a supplier change
Family enquiries do not wait for a software project to finish. Your operator needs agreed arrangements for urgent contacts, routine enquiries and unresolved work during the change. The software supplier, website provider and implementation agency may each control only part of that experience.
Identify a decision-maker at your funeral home and a responsible contact for each supplier. Agree who confirms the source information is available, who addresses exclusions and who accepts the finished scope. Your team also needs enough time to review the proposed access and practise its own responsibilities before relying on the new service.
Where a website is involved, include the contact routes and public information your team needs to retain. A working new homepage does not demonstrate that existing obituary links, enquiry forms or the provider’s at-need number are correct. For Ontario operators, keep the applicable BAO website information requirements in view during the change. Other provinces require their own assessment.
Ask what happens if a dependency is late or an agreed test reveals a material gap. The response may be to defer release, retain an approved temporary arrangement or narrow the first release with your approval. Do not accept a promise of zero interruption without a defined commitment and supporting terms. Agency project support is also separate from your funeral home’s responsibility for urgent family care.
Compare the cost of leaving as well as joining
A new subscription price can conceal a more expensive transition. Compare the full written commitment, including work charged by the outgoing supplier and access you may need to retain. No universal migration price or standard completion time can account for every funeral home’s systems, records and contract.
- Outgoing-provider charges: export assistance, termination obligations and any continuing access or archive fees.
- Incoming work: the agreed migration scope, review, staff handover and separately quoted corrections or additional history.
- Overlap: subscriptions, hosting or other services that may need to remain active during an approved transition.
- Third-party dependencies: obituary, website, accounting or other suppliers whose work is outside the main quote.
- Ongoing access: licences or support needed to use retained archives and deal with later questions.
Ask whether the amount is fixed for a defined scope, an estimate with assumptions or work charged as used. Record who authorises additional work when information is missing or incompatible. A low entry price with uncertain exit rights is not directly comparable with a quote that includes a usable archive and staff review.
Control of your business records does not mean ownership of a supplier’s software, pre-existing tools or third-party materials. Separate permitted data access and export rights from software licences, custom deliverables and publication rights. Have material contract questions reviewed before you accept the agreement.
An illustrative decision: what should this operator approve?
This is a hypothetical purchasing example, not a client case study. A two-location funeral home wants clearer responsibility for planning enquiries. Its current funeral management system remains suitable for arrangements and financial records. An incoming supplier offers to import contacts and provide an enquiry workspace.
The offer could meet a real need, but “contacts imported” leaves several decisions unresolved. Some planning conversations have a named staff contact, others have requested no further promotional communication, and historical documents sit with a separate provider. The operator should not assume that importing the contact list resolves those differences.
| Unresolved point | Useful written resolution | What it changes for the decision |
|---|---|---|
| What moves? | Permitted open planning enquiries and agreed context enter the new workspace; arrangement and financial records remain in the existing system. | The buyer can judge a limited enquiry project without assuming a complete operational replacement. |
| What happens to preferences? | The suppliers explain which current preferences and restrictions remain usable, and identify any gaps for operator review. | Uncertainty about contact permission remains visible rather than becoming automatic permission. |
| Where is older information? | The agreement identifies the retained archive, authorised access, included period and continuing costs. | The operator can decide whether that access is sufficient and affordable. |
| Who accepts the work? | A named operator reviews the agreed demonstration and exceptions; material gaps require a decision before release. | The purchase has an acceptance basis beyond a supplier saying the import is complete. |
In this example, proceeding with a limited scope may be reasonable if the confirmed service solves the enquiry problem and the remaining records stay appropriately accessible. If contact restrictions cannot be established or necessary history is inaccessible, the operator has a reason to resolve the gap before approving that scope. This is a conditional decision, not evidence that adding a CRM will improve revenue or that this arrangement suits every provider.
Agree what remains after the old account closes
Retaining everything indefinitely and deleting everything when a subscription ends are both poor assumptions. The OPC’s retention and disposal guidance explains that retention depends on the purpose and applicable requirements; there is no single period suitable for all records. Your operator and advisers must determine what the business needs or is required to retain.
The exit agreement should identify what returns to you, what remains in an approved archive, who may access it and what the supplier retains for a justified reason. Ask how temporary transfer copies, backups and subcontractor-held information are addressed, including timing and confirmation of disposal where appropriate. Do not request destruction that would conflict with an applicable recordkeeping duty or unresolved legal requirement.
An archive needs an owner after the project closes. Someone at your organisation should know how authorised access, corrections, family requests and later supplier questions will be handled. If access depends on keeping a paid service, include that obligation in the purchasing decision rather than discovering it after cancellation.
A decision you can take back to the supplier
A credible proposal lets you answer five questions in ordinary language:
- Purpose: which business problem does this move solve, and which existing systems remain?
- Coverage: what permitted information, history and context will be usable, and what is excluded?
- Responsibility: which supplier and operator contact handles each dependency, family-response concern and acceptance decision?
- Commitment: what are the full costs, rights, term and conditions for leaving both the old and new arrangements?
- Evidence: what agreed demonstration and documented exceptions will support your approval?
If a material answer is missing, request a clearer scope before committing. If the answers describe a smaller project than you first expected, assess that project on its own merits. A controlled decision with acknowledged limits is more useful than an expansive promise that no supplier has confirmed.
Canada Create’s funeral home CRM service starts with your existing tools and a separately agreed implementation scope. Compatibility, access, permissions and vendor participation need assessment before migration work can be promised. Share your business systems and priorities when enquiring, without family records or sensitive case details. Website and public-contact continuity can also be considered within an agreed funeral home marketing engagement.
Frequently asked questions
What software do funeral homes use, and which part is changing in a migration?
Funeral homes may run a funeral management system for cases and arrangements, a CRM for enquiries, and a separate website supplier for obituaries and contact routes. Each involves different records, suppliers and responsibilities. Before asking for a migration price, decide whether you are adding enquiry support, replacing the operational platform or changing the website supplier.
Should a funeral home replace its funeral management software or add a CRM?
It depends on the problem you need solved. If the existing system handles arrangements, contracts and financial records well, adding enquiry support may need only permitted enquiry details, contact preferences and staff responsibilities. Keeping a suitable existing system is a reasonable outcome, and a CRM project does not automatically require replacing it.
How do I choose the best approach to a funeral home software migration?
Judge each proposal on what your team will still be able to find, understand and use after the move. A promise to import contacts does not settle whether family relationships, documents, contact preferences, open enquiries or historical arrangements stay usable. Ask each supplier to separate website, CRM and operational records in the written scope and to list exceptions and costs.
What does a usable export from funeral office software look like?
A usable export lets authorized staff identify an enquiry, understand where it stands and find the supporting information included in the scope. A spreadsheet of financial totals or a folder of loose PDFs may be valid for its stated purpose while still leaving out correspondence or how documents belong together. Ask for a demonstration that also makes missing information visible.
Should a Canadian funeral home send real family files to get a software migration quote?
No. Ask for a demonstration with synthetic records or another specifically approved, privacy-appropriate example. Family files should never go through a general sales form just to obtain a price.
What happens to obituaries and photos when a funeral home changes digital suppliers?
Obituary pages, photographs, public links and media rights need their own decision, even when internal software stays the same. A media file alone may not carry its publication permission, page address or correction history. The written scope should say what stays public, which rights apply and which supplier controls it.
Who stays responsible for records when a funeral home moves to a new application?
The licensed operator keeps responsibility for family care, professional decisions and required records throughout the move. The operator and its advisers, not a software category, should determine the legal recordkeeping requirements. The agreement should also say what available means for each category, such as searchable staff access, a readable archive or a working connection to another supplier.
Is a free funeral home software migration really free?
A low or zero import price rarely covers everything the move involves. Staff time to approve records, documents excluded from the export, vendor charges and access to the old account after it closes can all add to the real cost. Compare the cost of leaving as well as joining, and get the exclusions in writing.