Skip to content
ByteScope

How-To

How To Move A Local Project To A New Machine Without Losing Anything

A repeatable checklist for migrating development environments, credentials and local data safely.

· Updated Sep 16, 2026 · 6 min read
Share this articleX
A laptop and an external drive side by side on a desk
Migrate in order: inventory, export, verify, wipe.Credit: ByteScope

Machine migrations go wrong in predictable ways. Work through this in order and nothing important gets left behind.

1. Inventory before you copy

List repositories, running services, local databases and anything holding credentials.

2. Export local state

pg_dump mydb > mydb.sql
tar -czf dotfiles.tar.gz ~/.config ~/.zshrc

3. Move secrets deliberately

  • Rotate anything you cannot account for.
  • Never move keys through chat or email.

4. Verify, then wipe

Rebuild each project from a clean clone and run its test suite before erasing the old machine.

More from ByteScope

The ByteScope Brief

Technology explained, once a week.

One email with the reporting and analysis worth your time. No hype, no daily noise.

No spam. Unsubscribe in one click.