Summary
Switching home care software providers can help agencies improve scheduling, caregiver management, billing, reporting, and daily operations. However, one of the biggest concerns during a software transition is what happens to the information already stored in the existing system.
Client records, caregiver profiles, visit histories, service authorizations, Electronic Visit Verification (EVV) data, billing information, and historical documentation may represent years of operational activity.
If agencies cannot export or transfer these records properly, changing software providers can become complicated, expensive, and disruptive.
Data portability in home care software refers to an agency’s ability to retrieve and transfer its information from one system to another in a usable format.
Before switching providers, agencies should understand what data can be exported, how it will be transferred, which records must remain accessible, and what responsibilities belong to each software vendor.
A structured data migration plan helps protect business continuity and reduces the risk of losing important operational information.
Introduction
Imagine a home care agency has used the same software for five years.
During that time, the agency has accumulated thousands of caregiver visits, client records, service schedules, billing transactions, and supporting documents.
As the agency grows, its existing platform becomes difficult to manage. The leadership team decides to evaluate another home care management system.
The new software looks promising.
It offers a more organized interface, improved operational workflows, and features that better match the agency’s current needs.
But during the transition discussion, the agency discovers that its existing provider may not allow all historical information to be exported in a usable format.
Some records can be downloaded as spreadsheets, while other information is available only through individual PDF files.
Historical EVV records, billing adjustments, and attached documents may require additional work.
Suddenly, the software transition becomes more complicated than expected.
This is why data portability should be evaluated before an agency commits to switching home care software providers, not after the contract has been signed.
What Is Data Portability in Home Care Software?
Data portability is the ability to retrieve, transfer, and reuse information stored in a software system.
For home care agencies, this may include moving information from an existing platform into a new home care management system.
Data portability involves more than downloading a file.
The exported information must also be understandable, complete enough for its intended purpose, and suitable for import into the replacement platform or for reliable archival access.
For example, an agency may successfully export a list of client names but still be unable to transfer the associated service authorizations, caregiver assignments, or historical visit records.
A useful data portability process considers the relationships between records, not just the number of files exported.
Why Does Data Portability Matter When Changing Software Providers?
Home care agencies rely on historical and current information to coordinate services, support billing, respond to audits, and manage day-to-day operations.
If information is incomplete or inaccessible during a transition, agencies may experience scheduling confusion, billing delays, missing documentation, or additional administrative work.
Data portability also affects vendor flexibility.
An agency that can retrieve its information in usable formats is better positioned to evaluate alternative platforms without being unnecessarily dependent on its current provider.
However, agencies should not assume that every record can be transferred directly into a replacement system.
Some historical information may need to remain in a secure archive rather than being imported into the new platform.
1. Confirm Who Controls the Agency’s Data
Before beginning a software migration, agencies should review their existing agreement to understand their rights to access, export, retain, and transfer information.
Important questions include:
- What does the contract say about agency data and vendor access?
- Can the agency request a complete export?
- Are there additional charges for data extraction?
- How long will data remain available after termination?
- Does the vendor provide migration assistance?
- What happens to remaining copies after the contract ends?
The contract may distinguish between agency-provided information, vendor-created system data, proprietary software components, and other categories.
Agencies should review these provisions carefully rather than assuming that paying for a software subscription automatically guarantees unrestricted export of every record in the system.
2. Check Which Client Records Can Be Exported
Client information is one of the most important parts of a home care software migration.
Agencies may need to transfer names, contact information, emergency contacts, service details, care preferences, payer information, and other relevant records.
The exact information required depends on the services provided.
Before switching platforms, agencies should request a detailed export inventory.
This helps determine which fields are available, which records are missing, and whether information can be mapped to the replacement system.
A client list alone is rarely enough to support a complete operational transition.
3. Review Caregiver and Staff Data
Caregiver information is another important part of the migration process.
Home care agencies may maintain employee contact details, availability, qualifications, assigned clients, scheduling information, and training records.
When this information is incomplete, scheduling teams may need to rebuild caregiver profiles manually.
Agencies should verify which records can be exported and whether the new software can accommodate the same information.
Sensitive personnel information should be transferred only when necessary and through appropriate security controls.
4. Verify Historical Visit and Attendance Records
Visit history is particularly important for agencies that need to support billing, audits, or service reviews.
Historical information may include scheduled visits, actual visit times, caregiver assignments, attendance records, and completed service documentation.
Agencies should determine whether these records can be exported with their original dates, identifiers, and relevant relationships intact.
For example, a spreadsheet containing visit times may be insufficient if it does not identify the client, caregiver, service type, or associated claim.
The objective is to preserve enough context for the records to remain meaningful.
5. Check EVV Data Portability
Electronic Visit Verification records require special attention when switching home care software providers.
Federal EVV requirements apply to specified Medicaid-funded personal care and home health services that require in-home visits.
Depending on the state’s implementation, agencies may need to maintain information about service type, recipient, provider, date, location, and start and end times.
Before migrating, agencies should determine whether relevant EVV data can be exported and whether it includes associated corrections, exceptions, and other supporting information where applicable.
They should also confirm how the new platform connects with the required state or payer EVV system.
Moving historical EVV records into a new software platform does not automatically mean those records have been accepted by the applicable Medicaid program.
Agencies should verify state-specific requirements and maintain appropriate access to historical records.
6. Review Billing, Claims, and Payment History
Billing information is often more complex to migrate than basic client profiles.
An agency may have years of claims, payment records, denials, adjustments, outstanding balances, and payer-specific details.
Before switching providers, the billing team should identify which information must remain available for ongoing financial operations.
Particular attention should be given to claims that have been submitted but not fully resolved.
For example, a claim may still be awaiting payment, reconsideration, or an adjustment when the agency begins using the new system.
The migration plan should explain which system will manage these outstanding transactions and how the agency will prevent duplicate billing.
7. Confirm Whether Documents and Attachments Are Included
Home care software may contain uploaded documents, signed forms, assessments, care plans, and other supporting files.
These documents are not always included in standard database exports.
An agency might receive client demographic information but discover that supporting attachments must be downloaded separately.
Before switching providers, agencies should verify whether documents can be exported in bulk and whether they retain their associated client identifiers and dates.
It is also important to determine whether the exported files will remain readable without access to the original software.
8. Understand Export File Formats
The format of exported information can significantly affect migration effort.
Common formats include CSV, Excel, JSON, XML, and PDF.
Structured formats such as CSV, JSON, or XML can be useful for transferring information between systems, provided the data fields are documented and compatible.
PDF files may be appropriate for preserving readable historical records but are often less suitable for importing structured data into another platform.
Agencies should ask both providers which formats are supported.
They should also request a sample export before committing to the full migration.
A successful export does not guarantee that the replacement system can import every field.
9. Ask About Data Mapping and Compatibility
Different software platforms may organize information differently.
For example, one system may store caregiver availability as separate daily schedules, while another may use recurring availability rules.
Similarly, service codes, payer information, and client statuses may use different naming conventions.
Data mapping is the process of identifying how information from the existing system corresponds to fields in the new system.
Agencies should clarify who will perform this work and how unmatched or incompatible fields will be handled.
A documented mapping plan can reduce errors and make the migration easier to verify.
10. Review HIPAA and Data Security Responsibilities
Home care agencies handling protected health information must consider applicable privacy and security obligations during a software transition.
Where HIPAA applies, agencies should review their responsibilities and the role of each technology vendor, including applicable business associate agreements.
Data exports should be transferred and stored using appropriate safeguards.
Access should be limited to authorized individuals, and temporary migration files should be managed according to approved retention and disposal procedures.
Agencies should also understand how the former provider will return, retain, or destroy protected health information when the relationship ends, consistent with the applicable agreement and legal requirements.
Not every home care organization has identical HIPAA obligations, so agencies should assess their specific circumstances.
11. Confirm Historical Record Retention Requirements
Changing software does not eliminate an agency’s responsibility to retain records for required periods.
Record retention requirements may depend on state licensing rules, Medicaid programs, Medicare participation, contracts, and other applicable laws.
Some records may need to remain available for years after services have ended.
Agencies should decide whether historical information will be imported into the new system, stored in a secure archive, or retained through another compliant arrangement.
They should also confirm that authorized staff can retrieve records when needed.
A file that has been exported but cannot be located or interpreted later may provide little practical value.
12. Test the Migration Before Going Live
A software migration should not rely entirely on the assumption that all exported information will transfer correctly.
Agencies should conduct a test migration using an appropriately protected sample of records.
The test should verify client information, caregiver assignments, service authorizations, schedules, visit records, and other relevant data.
Teams should compare the original records with the imported information.
For example, if the old system shows 150 active clients, the new system should contain the expected active client records after migration.
However, record counts alone are not enough. Staff should also verify critical field values, relationships, and representative historical records.
13. Plan for Unfinished Visits and Claims
One of the most important migration decisions is selecting the transition date.
If the agency changes platforms in the middle of active scheduling and billing cycles, some records may exist in both systems.
This can create confusion about which platform is the authoritative source.
Agencies should establish clear procedures for scheduled visits, completed but unbilled services, pending claims, and outstanding payments.
The transition plan should identify which system will be used for each activity during the changeover.
A defined cutover process helps reduce duplicate entries and inconsistent records.
14. Confirm Post-Migration Support
Data migration problems do not always become visible immediately.
Staff may discover missing records, incorrect service codes, or unexpected scheduling differences after the new platform goes live.
Agencies should understand what support the new provider offers during and after implementation.
Important considerations include the support period, issue escalation process, responsibility for correcting migration errors, and any additional charges.
A clear support agreement can help agencies resolve problems without unnecessarily interrupting daily operations.
Home Care Software Data Portability Checklist
Before switching providers, agencies can use the following checklist to organize their evaluation.
Area | What to verify |
Data access | Contractual rights to retrieve and export records |
Client profiles | Demographics, contacts, service information, and relevant history |
Caregiver records | Staff profiles, availability, qualifications, and assignments |
Scheduling | Active schedules, recurring visits, and future assignments |
Visit history | Completed visits, attendance, and supporting documentation |
EVV | Historical data, exceptions, and state-specific integration requirements |
Billing | Claims, payments, adjustments, and outstanding transactions |
Documents | Attachments, signed forms, and historical files |
Export formats | CSV, Excel, JSON, XML, PDF, or other supported formats |
Security | Protected transfer, authorized access, and applicable agreements |
Retention | Continued access to records for required periods |
Migration testing | Validation of critical fields, records, and relationships |
Vendor support | Responsibilities, timelines, costs, and post-migration assistance |
Example: Switching From One Home Care Software Provider to Another
Consider a hypothetical home care agency managing 200 active clients and 75 caregivers.
The agency decides to replace its existing software because its operational needs have changed.
Before signing the new contract, the agency requests a sample export from its current provider.
The operations team reviews client profiles, caregiver records, and scheduling information.
The billing department examines outstanding claims and historical payment records.
The compliance team identifies which documents and EVV-related records must remain accessible.
Next, the agency works with the replacement provider to map the available data fields.
A test migration is completed, and staff compare selected records between the two systems.
The agency identifies several document attachments that cannot be imported directly.
Instead of losing them, the team establishes a secure archival process that preserves authorized access.
After resolving the identified issues, the agency selects a cutover date and prepares staff for the transition.
This example demonstrates why data portability planning should begin before implementation.
Common Mistakes Agencies Make During Software Migration
Home care agencies may encounter unnecessary problems when they focus only on the features of the replacement software.
Common mistakes include assuming all data can be exported, failing to check historical records, overlooking EVV requirements, and not reviewing unfinished billing transactions.
Another mistake is canceling access to the existing platform before confirming that necessary information has been transferred or securely archived.
Agencies should also avoid relying on verbal assurances about migration capabilities.
Written confirmation of supported data types, formats, responsibilities, costs, and timelines can reduce misunderstandings.
Questions to Ask a New Home Care Software Provider
Before selecting a replacement platform, agencies should ask practical questions about data portability and implementation.
- What information can be imported from our current software?
- Which file formats does your migration process support?
- Can you migrate historical visit and attendance records?
- How are existing client and caregiver records mapped?
- Can billing history and outstanding claims be transferred?
- What happens to documents that cannot be imported?
- How will EVV integrations be configured for our state and payers?
- Who is responsible for testing and validating migrated information?
- What migration assistance is included in the implementation cost?
- How can we export our information if we decide to leave your platform in the future?
The final question is especially important.
A good software transition should solve today’s operational challenges without creating unnecessary barriers to a future transition.
How myEZcare Can Support Home Care Agencies During a Software Transition
Selecting new home care software involves more than comparing features.
Agencies need a platform that supports their operational requirements while providing clarity about implementation, data handling, and ongoing workflows.
myEZcare helps home care agencies manage connected activities involving client information, caregiver scheduling, attendance, EVV-related processes, documentation, billing, and reporting.
These operational capabilities can help agencies organize the information used across daily service delivery and administrative processes.
When evaluating myEZcare as a replacement platform, agencies should discuss their existing system, available export formats, historical records, state-specific EVV requirements, and migration needs with the implementation team.
Import compatibility, historical data migration, document handling, and implementation support should be confirmed for the agency’s specific situation rather than assumed.
Considering a switch from your current home care software? Explore myEZcare and discuss how its home care management workflows may support your agency’s operational needs.
Conclusion
Data portability is one of the most important considerations when switching home care software providers.
A new platform may offer better workflows and operational capabilities, but agencies also need confidence that existing information can be retrieved, transferred, or securely preserved.
Client records, caregiver information, schedules, visit histories, EVV data, billing records, and supporting documents all require careful review.
Before committing to a new provider, agencies should verify export capabilities, data formats, contractual rights, security responsibilities, migration support, and historical record access.
The goal of switching home care software is not simply to move information into a new system. It is to maintain reliable records and uninterrupted operations while creating a stronger foundation for the agency’s future needs.
