Linux Conversion Handoff Checklist for an Unsupported Windows PC

Once a Windows PC has already been approved for Linux migration, the remaining job is execution and documentation.

The conversion should end with a handoff record that shows what was backed up, what was installed, what was tested and what limitations remain.

That is different from deciding whether Linux is a good idea in the first place.

Record the pre-conversion state

Before erasing or repartitioning anything, record:

• manufacturer and model;
• serial number if appropriate;
• CPU;
• RAM;
• storage device and health;
• Windows version;
• Windows activation status where relevant;
• major peripherals;
• important user accounts.

Photographing the system-information screen can be useful.

Do not record passwords in the service notes.

Confirm the backup

List what was backed up.

Typical categories include:

• documents;
• photos;
• downloads that matter;
• browser bookmarks or profile data;
• email archives where applicable;
• application data;
• license information;
• encryption recovery keys if relevant.

Then verify representative files from the backup.

"Backup completed" is not enough if nobody has opened the copy.

Record the live-test results

Before installation, document the hardware checks already performed.

Mark pass/fail for:

• Wi-Fi;
• Ethernet;
• audio;
• microphone;
• webcam;
• graphics;
• external display;
• Bluetooth;
• suspend/resume;
• printer/scanner where required;
• removable storage.

If a known limitation was accepted, write it down.

Record the installed Linux system

After migration, note:

• distribution;
• version;
• desktop environment if relevant;
• installation date;
• disk layout;
• encryption status;
• user account created;
• update status.

This makes later support much easier than asking the owner to remember what was installed.

Restore only verified data

Restore the user's required files from the backup.

Then open representative items:

• document;
• spreadsheet;
• photo;
• PDF;
• project file.

Check permissions and ownership after restoration.

A file that exists but cannot be opened by the user is not a completed restore.

Reinstall required applications

Use the pre-migration software audit.

Install only the applications the owner actually needs.

For browser-based services, verify login and basic use.

For replacement applications, confirm that representative files open correctly.

Test the completed workflow again

Repeat the real-world acceptance test after installation.

The installed system may behave differently from the live environment because of:

• proprietary drivers;
• updates;
• different kernel packages;
• installed applications;
• power-management configuration.

Test the finished machine, not only the installer.

Record known limitations

Examples:

• vendor utility unavailable;
• one special printer feature unsupported;
• Windows-only application requires another machine;
• fingerprint reader not configured;
• game compatibility not guaranteed.

A handoff record should make limitations visible rather than letting the owner discover them later.

Give the owner recovery information

Provide clear notes for:

• how to run updates;
• where backups are stored;
• what recovery media exists;
• what distribution/version is installed;
• where to ask for support.

Do not hand over administrator credentials in an insecure format.

Final acceptance checklist

Before the machine leaves:

• backup verified;
• Linux installed and updated;
• user data restored;
• browser works;
• audio works;
• networking works;
• suspend/resume tested;
• required peripherals tested;
• required applications tested;
• known limitations documented.

The migration is complete when the finished computer passes the owner's required workflow—not when the installer reaches the desktop.