Most people manage devices reactively. Something breaks, you buy a replacement in a hurry, the old one goes in a drawer, and the cycle repeats. Data gets stranded, money gets wasted on the wrong specifications, and every few years there's a bad week where nothing works.
A lifecycle plan is just four checkpoints applied to every device you own. It takes an hour to set up and saves the bad weeks.
Stage 1: Buy
Decisions made here are the ones you can't undo.
Size the storage for the whole life of the device, not for today. This matters most on machines with soldered, non-upgradeable drives — which is most modern laptops, all phones, and all tablets. Buying the cheapest storage tier is the decision people regret most, because there's no fixing it later. Check what you're currently using and buy at least double.
Check what's upgradeable before assuming you can add memory or storage later. Increasingly, nothing is.
Consider the support window. Phones and tablets receive operating system and security updates for a defined period, which varies considerably between manufacturers and models. A device that stops receiving security updates is a device you shouldn't be using for anything sensitive. Buying a model with a longer support window is often better value than a cheaper one with two years left.
Buy the drive and the backup at the same time as the computer. A new machine without a backup plan is a new machine accumulating data with no protection. Budget for it up front.
Record the details immediately — model, serial number, purchase date, warranty period, where you bought it. Ten seconds now, and it's what you need for insurance, warranty claims, or a police report.
Consider refurbished. For most household needs, a well-specified refurbished machine outperforms a new budget one at the same price, and it's environmentally better. Check the warranty and the remaining support window.
Stage 2: Set up
Covered in detail elsewhere; the lifecycle-relevant items:
- Encryption on, recovery key saved to your password manager and printed
- Backup configured before there's anything to lose
- Folder structure built before there are files
- Find-my-device enabled
- Automatic updates on
- Recorded in your device register — see below
The single most valuable habit: set up the backup on day one, before the device has data on it. Backups added later never quite get done.
Stage 3: Use
The maintenance rhythm that keeps a device healthy through its life.
Monthly, five minutes:
- Check the backup ran and the last success date is recent
- Check free space is above 20%
- Install pending updates
- Restart
Quarterly, fifteen minutes:
- Empty Downloads and the trash
- Review startup items
- Restore one file from backup and open it
- Check drive health
Annually, thirty minutes:
- Run a disk analyzer and note what's growing
- Review whether the device still suits what you use it for
- Check the remaining support window
- Note the device's age
- Clean the vents and fans physically
The support-window check is the one people skip and it's the one that determines when you should replace. A phone that stopped receiving security updates eighteen months ago is a risk regardless of how well it works.
Stage 4: Retire
Retirement starts before the device dies, and that's the whole point.
Plan replacement rather than reacting to failure. Signals that it's time:
- Security updates have stopped or will stop within a year
- The battery no longer lasts a useful working session and can't be replaced economically
- Storage is chronically full with no fix available
- It's too slow for what you need after a genuine clean-up
- Repairs would cost a meaningful fraction of a replacement
- It's four to six years old and showing multiple symptoms
Replacing on your schedule means you migrate calmly with both devices working. Replacing after a failure means you migrate from a backup under time pressure, and you discover the gaps in that backup at the worst moment.
The retirement sequence:
- Buy the replacement while the old device still works
- Take a full backup of the old device and verify it
- Move authenticator codes to the new device and test one
- Migrate or set up fresh
- Keep the old device working for a month — this is the step that catches what migration missed
- Take a final backup and keep it six months
- Deauthorize software, sign out of every account, remove from device lists
- Wipe it properly
- Donate, sell, trade in, or recycle — never bin it
- Update your device register
Step five is the one people skip and regret. A working old device is the best possible backup of itself.
The household device register
One file, 01 Admin/Devices.md, listing everything:
| Device | Purchased | Serial | Storage | OS support until | Backup | Notes |
|---|---|---|---|---|---|---|
| MacBook Air | 2023-09 | XXXX | 512GB | ~2030 | Time Machine + cloud | main machine |
| iPhone | 2024-03 | XXXX | 256GB | ~2029 | iCloud, verified 2025-04 | |
| iPad | 2020-11 | XXXX | 64GB | ends 2026 | iCloud | replace next year |
| NAS | 2022-06 | XXXX | 8TB | — | cloud backup | 4 drives, oldest 2022 |
| Backup drive A | 2023-01 | — | 4TB | — | is the backup | replace 2028 |
| Backup drive B | 2023-06 | — | 4TB | — | off-site at Mum's | swap monthly |
| Old iPhone | — | XXXX | — | — | wiped 2024-08 | donated |Fifteen minutes to build, and it does four jobs:
It tells you what to replace next, from the support-window column.
It tells you what's protected, from the backup column. Blank cells in that column are the work.
It's what you need after a theft or fire — serial numbers for insurance and police reports.
It tells you which drives are due for replacement, which is otherwise impossible to remember.
Review it annually. Add a row when something new arrives; update the row when something is retired.
The three-drive cycle
Storage devices have their own lifecycle, and it's the one most often neglected because drives keep working right up until they don't.
Buy — NAS-rated or backup-appropriate drives, sized at twice your data, not all from the same batch.
Use — labelled with contents and purchase date, encrypted, verified annually by plugging in and opening files.
Retire at three to five years, regardless of apparent health. Copy forward to the new drive, verify by opening files, then destroy or securely wipe the old one.
The reason to replace a working drive is that copying from a healthy drive takes an hour and copying from a failing one may not be possible at all.
Budgeting for the cycle
Devices are a recurring cost, and treating them as occasional emergencies is what makes them painful.
Rough planning horizons:
- Phones: 3–5 years
- Laptops: 4–6 years
- Tablets: 4–6 years
- Drives: 3–5 years
- Routers: 4–6 years, or whenever firmware updates stop
- NAS: 5–8 years for the unit, 3–5 for the drives inside it
Divide the replacement cost by the expected years and you have an annual figure. Set that aside and replacement becomes a purchase rather than a crisis.
The register makes this concrete: looking at it once a year tells you what's coming due, which turns an unpredictable expense into a scheduled one.
The one-hour setup
If you're starting from nothing:
- Build the device register. Every device, with purchase dates and serial numbers where you can find them.
- Fill in the backup column honestly. The blanks are your gap list.
- Check the support window for every phone and tablet.
- Note the age of every drive.
- Set three recurring reminders: monthly backup check, quarterly restore test, annual register review.
That's the whole system. It's not sophisticated, and it converts device management from a series of surprises into a schedule.
The point of all this
Devices are temporary. Every one you own will be replaced, and the average working life is somewhere between three and six years.
Your data is not temporary. It has to travel across all of those devices, intact, for decades.
The lifecycle plan exists to make sure that transfer keeps happening — that no device carries the only copy of anything, that replacement happens on your schedule rather than after a failure, and that nothing gets stranded in a drawer because the machine it lived on stopped booting.
That's the whole idea, and it's the thread running through every article on this site.