Getting Started: Migration from KidsChores

Use this guide if you are moving from the legacy KidsChores integration to ChoreOps.

Note

This page is intentionally migration-only so it can be removed cleanly in a future release.

---

What happens during migration

When you add ChoreOps, the integration checks for existing data files.

• If a ChoreOps data file already exists, ChoreOps uses that file.
• If no ChoreOps data file exists, ChoreOps can detect legacy KidsChores data and offer direct import/migration. Selecting either the current_active file or in the dropdown for migrate_from_kidschores will import the Kidschores data.

---

Data safety and side-by-side behavior

Migration is designed to be non-destructive for legacy files:

• KidsChores data files are left in place.
• ChoreOps creates and uses its own data file after migration.
• You can technically run both integrations side by side during setup and validation.

Warning

Side-by-side operation is useful during transition, but avoid long-term dual operation unless you understand the implications of maintaining two independent data stores.

Challenges migrated to periodic badges

Note

During migration, existing Challenge records are converted to equivalent Periodic Badge tracking to preserve intent and progress behavior where possible. They will be returning in a future release completely reimagined from their original implementation in KidsChores

---

How to migrate

1. Install ChoreOps
2. Add the ChoreOps integration in Home Assistant
3. In Data Recovery Options, choose the migration/import option when legacy KidsChores data is detected
4. Complete setup and validate entities, workflows, and dashboards

If no migration option appears, verify your legacy KidsChores files still exist in your Home Assistant storage path.

---

Cleaning up legacy KidsChores files

After you confirm ChoreOps is working, you can remove legacy files if desired.

Option 1: Use ChoreOps backup/restore delete flow

In Settings → Devices & Services → Integrations → ChoreOps → Configure → General Options, the backup/restore delete action can detect legacy backup artifacts and allow deletion from within ChoreOps.

Option 2: Manual deletion

You can also delete legacy files manually using your preferred file-management tools.

---

Related docs

• Installation and Setup
• Backup and Restore Reference
• Quick Start Guide

---

Last Updated: February 2026