An old computer often holds years of material that never needs to travel everywhere. Preparing files for Googlebook can be a selective process: move current work conveniently, preserve archives safely and avoid paying to synchronise files that rarely change.
Quick Answer
Separate active documents, shared work and long-term archives before choosing transfer routes. Use supported local storage for material that does not need cloud access, with a second independent copy for important data. Confirm complete file content, drive support and application readability before depending on an offline archive.
📁 Sort by use rather than by file age alone
A recent download may be disposable, while a ten-year-old document may be irreplaceable. Group files by purpose: current work, reference material, personal originals and material that can be downloaded again. This creates a storage plan based on value rather than simply sweeping every folder into one upload.
Keep active projects together. A video timeline or design document can depend on assets in several locations, and copying only the visible project file may leave it unusable. Use the application's packaging method where available, or collect the required assets into a clear archive structure.
Create a small transfer folder containing the work needed soonest. This lets you verify the new device before spending time on large media collections. Keep a plain inventory of the major folders and their source location so the archive remains understandable months later.
Compare external SSD options against the size of the archive and its backup, not just the current working folder. Capacity planning is easier once duplicate downloads and replaceable installers have been distinguished from originals.
☁️ Resolve cloud placeholders before going offline
A file visible in a desktop folder can be represented by a placeholder while its content remains online. Copying a folder view without confirming downloads can produce an incomplete offline plan. Identify which cloud service manages the source and use its supported method to obtain full local copies.
Open representative files with the source computer disconnected after they have been deliberately made available locally. This is a practical check that the content exists rather than being fetched invisibly each time. Do not delete cloud copies as part of that test.
Cloud storage still has a useful role for current collaboration or access from several devices. The choice is selective: a small set of frequently edited documents may benefit far more than a large static video archive. Uploading to Drive also consumes storage, so account capacity belongs in the plan.
Keep organisational or sensitive material in a location authorised for it. Personal convenience does not establish permission to copy a work archive into a private account. Choosing local storage can reduce uploads, but still requires appropriate access control and backup.
🔌 Establish a supported local storage path
Before relying on an external drive, confirm the device supports its connection and file system. Encryption can add another dependency if unlocking requires a Windows-only utility. A matching USB connector does not answer those questions.
Copy a small mixed batch first: a document, photo, large video and project folder. Open them through the applications that will actually use them. Then try saving a new file back to the intended working location. Read access alone does not prove the workflow can write changes where expected.
For the laptop itself, compare available laptop configurations with enough room for active work and temporary files. An archive drive can hold historical material, but a slow or inconvenient connection may be unsuitable for daily editing. Decide which files stay on the internal storage for practical reasons.
✅ Verify copies before reorganising the archive
During migration, copy rather than move. Compare the destination structure with the source, inspect file sizes and open examples from each important group. For especially valuable collections, use checksums to compare complete file bytes where supported tools make that practical.
Keep an independent backup before renaming thousands of files or consolidating folders. Synchronisation can reproduce an accidental deletion, while a separate retained copy gives you a recovery point. A drive permanently used as the only working archive is not, by itself, a second copy.
Finish with a short index explaining what lives on the laptop, what remains on external storage and what is shared online. This prevents the same search from becoming a repeated hunt across several accounts. The result is a smaller, clearer migration that preserves the original material without forcing every file into the cloud.
Frequently Asked Questions
Must every old file be placed in Google Drive?
No. Choose storage by purpose. Current shared work may suit cloud access while archives can remain on supported local storage with backups.
Does a cloud placeholder contain the full file?
Not necessarily. A placeholder can represent data still stored online, so obtain the complete content before relying on an offline archive.
Should files be moved or copied during migration?
Copy first. Retaining the source provides a recovery path until the destination files and required applications have been verified.
Can file counts alone prove the transfer is intact?
No. Counts detect missing entries, but opening files and, where appropriate, comparing checksums provide stronger verification.
Does a USB-C port guarantee an archive drive will work?
No. The drive, data cable, file system and encryption method must all be supported by the intended device and software.
Keep archives local and move active work deliberately?
Compare Evetech laptops and external SSDs around the active files you need nearby and the archive copies you want to preserve.