Maple Is Shutting Down: A Family Migration Process for Household Tasks

Move active household work out of Maple before December 31, 2026, then verify the destination with each family member before deleting anything. Maple’s official site says the service will sunset on that date, accounts will become inaccessible, and data will be deleted. This is not a normal feature comparison. Continuity and a clean export come first.

Freeze the scope before you migrate

List what the family currently relies on: tasks, recurring routines, calendar connections, notes, meal plans, and anything else visible in the account. Mark each item active, archive, or disposable. Assign one migration lead and one checker, but let the owner of sensitive material decide whether it should move.

Take screenshots of critical recurring setups as a fallback, without exposing private family information in an open photo library. Record account members and integrations. The official Maple notice says data remains accessible until the shutdown and recommends exporting or transferring it before then. Follow the guidance Maple provides to your account rather than assuming every data type exports the same way.

Choose a destination by the work that must survive

If recurring chores, ownership, and household bills are the core record, test HomeCo with a small set first. If the family’s critical system is mainly an external calendar, preserve that calendar in its native service and use a household tool only for operations. Do not rebuild obsolete projects just because they exist.

Create a mapping table: Maple item, destination, new owner, recurrence checked, attachment checked, and accepted by. Recurrence deserves manual verification. A task that imported once but lost its schedule is not migrated.

Complete a parallel week and close access carefully

For one week, keep Maple read-only in practice while new work happens in the destination. Compare due items each evening. Ask every household member to complete, reassign, and comment on one real task. Fix notification and accessibility issues before declaring success.

After acceptance, save the permitted archive in controlled storage and disconnect integrations that no longer need access. Do not wait for the final day. The deadline is a backstop, not a project plan. HomeCo can be one candidate for the operational portion, but the right migration may use more than one destination if Maple held several kinds of family information.

Set an internal completion date at least several weeks before shutdown. That buffer leaves room for a forgotten device, an absent family member, or an export that needs interpretation. Keep a migration log with date, item count, exceptions, and checker initials. When the family signs off, send one clear message naming the new authoritative system. Otherwise, someone will keep adding tasks to the familiar app while others have already moved.

How HomeCo helps

Use HomeCo to keep the household owner, due date, shared cost, and follow-up visible where those functions fit this process. Link the plan to a real task instead of burying it in chat. The related HomeCo guide, building a household agreement , offers a useful next step.

HomeCo should support the family’s decision, not make it. Keep benefit records, medical authorizations, tax evidence, and legal documents in the systems required by the relevant organization. Review household access whenever someone moves out, a caregiver role ends, or private information no longer needs to be shared.

FAQ

Can we wait until December to export?

You could lose time to account, device, or format problems. Start early enough to test and correct the new system.

Will HomeCo import Maple data automatically?

Do not assume an import exists unless current HomeCo documentation or support confirms it. Plan for a controlled manual rebuild of active items.

What should we delete instead of moving?

Expired shopping items, completed one-off tasks, duplicates, and records the family no longer has a reason or right to keep are good review candidates.