Explore Evidently

Switching care software

A practical checklist for switching care software.

Start with a written record of what must move, who will check it and how care will continue during the change. This checklist helps a domiciliary care agency plan the conversation with both suppliers before committing to a launch date.

Talk through your migration
Published by Evidently on Updated and checked

This is our practical planning checklist, with the regulatory source linked below. It describes suggested checks, not a certified migration method or a guarantee of compliance. The CQC reference applies to services in England.

01

Define what a successful switch needs to do.

Write down the three problems you want to solve and turn each into a task to demonstrate. For example, use a fictional assessment, a cancelled morning visit and a completed pay period. Ask each supplier to show the steps, the person responsible and the final output. Record any manual work or missing capability alongside the quoted price.

  • Care manager: follow a source assessment into a reviewed care plan and check how later changes are recorded.
  • Coordinator: change a visit and check staff availability, travel, required skills and communication with the team.
  • Office team: follow delivered hours into the billing or payroll output your agency actually uses.
  • Decision maker: agree which requirements are essential for launch and which can wait.
Try a fictional cover-planning example
02

Get the exit and onboarding scope in writing.

Ask the current supplier about notice, the date access ends, export formats, charges and support. Ask the new supplier exactly which files it can accept. A downloadable report may be useful for reading without being suitable for import. Do not treat an available CSV button as proof that every record or attachment will transfer.

  • List the data categories, date ranges, expected volumes and file formats before agreeing an import.
  • Confirm responsibility for preparing files, correcting errors, checking the result and doing any manual entry.
  • Include overlap subscriptions, additional training, archive access and staff time in the transition budget.
  • Agree a secure transfer route and authorised recipients before sharing identifiable records. Keep care and staff records out of public enquiry forms.
03

Build a record-by-record migration register.

Use one row for each category below. Give it an owner, export date, destination, checking method and sign-off status. Separate information needed for live care from historical records that will remain in an agreed archive. An archive still needs to be readable and retrievable by the right people.

  • Client details and contacts: check identity matching, duplicates, active status and who may access each record.
  • Current care plans, assessments and risks: identify the version in use, its source and any review outstanding.
  • Medication information and administration history: agree the scope separately and have authorised staff verify the information needed for continuity under your medicines procedures.
  • Rotas and visits: distinguish recurring patterns, future bookings and completed visit records. Check cancellations, double-up visits and time-sensitive arrangements.
  • Workforce: scope availability, employment documents, training evidence, competencies and expiry dates. Avoid copying records simply because they are present.
  • Finance and evidence: account for invoice periods, payroll outputs, attachments, timestamps and audit history. Confirm anything that cannot be imported and how it will be retained.
04

Check the meaning of the records, as well as the totals.

Compare the agreed export inventory with the imported result and investigate missing or rejected rows. Then have the responsible team check the content and relationships. Matching totals alone will not reveal a plan attached to the wrong person, a missing attachment or an outdated instruction. Agree the checking method for each category, including individual review of information relied on for live care.

  • Check source and destination identifiers, dates, document versions and access permissions.
  • Record exceptions, their owner and their resolution. Do not mark a category complete while an essential discrepancy remains unresolved.
  • Keep a dated record of what was checked and who accepted it. Reconcile changes made after the first export before switching the live workflow.

For regulated services in England, CQC’s guidance includes keeping care records secure, accurate, complete and up to date. The migration checks above are Evidently’s practical suggestions for planning a change, not CQC’s own checklist. Source: CQC Regulation 17: good governance

05

Prepare the team and agree the changeover.

Name the person who decides whether the agency is ready, the supplier contact and the out-of-hours escalation route. Practise with fictional records first. Each role should know where to read current information, where to record new activity and how to report a problem. Avoid leaving staff to guess which of two systems is the live record.

  • Before launch: check staff access and devices, train each role and confirm the first live rota and current care information.
  • At changeover: record the agreed time, where new entries belong, and how late changes and unfinished records will be reconciled.
  • If checks fail: use the agreed delay or fallback plan, communicate it to everyone affected and resolve the issue before relying on the new workflow.
  • After launch: review issues from the first shifts, reconcile missing activity and confirm the team can retrieve required historical records.
06

Plan historical access before closing the old account.

Confirm where retained records will live, who can retrieve them and how you will test retrieval. Use your organisation’s retention policy and applicable obligations to decide what to keep and for how long. Do not assume a single retention period covers care records, workforce files and financial information. Confirm the supplier’s return and deletion arrangements before access ends.

  • Try retrieving a historical record with its attachments and relevant audit information.
  • Document access controls, backup responsibilities and the owner of future retrieval requests.
  • Close the migration register only when essential checks, outstanding issues and archive arrangements have an agreed outcome.
07

What Evidently includes, and what we agree with you.

Standard onboarding includes workspace setup, help importing an agreed set of compatible records and one remote team training session. We review the exports available before confirming scope. Additional work needs a separately approved quote. We do not promise an instant transfer, a direct connection to your previous supplier or that every historical record can become an editable Evidently record.

  • Bring your current system, approximate active service-user count, workflows and desired timing to the first conversation.
  • Ask us to demonstrate any essential workflow and record the answer before subscribing.
  • Confirm the subscription, onboarding responsibilities and Ada usage allowance in the written quote. Ada assists with drafts and proposals that people review.
Discuss your agency’s requirements

A little more detail.

How long does switching care software take?

There is no reliable single timescale. It depends on notice periods, export availability, record quality, the scope of manual work, training and your team’s checks. Agree milestones and a readiness decision before setting a firm changeover date.

Can we transfer all our historical records?

Confirm this category by category with both suppliers. Some information may be suitable for import, some may need manual review and some may need a separate archive. Ask specifically about attachments, medication administration history, timestamps and audit trails.

Should we use both systems during the transition?

An overlap may help with preparation and checking, but it needs a clear plan. Define the live record for each workflow and the time it changes. Uncontrolled duplicate entry can create conflicting information. Agree reconciliation and fallback arrangements with your responsible team.