---
title: Fast Transfer of Home, Apps & Settings Between Linux Distros
siteUrl: https://logzly.com/distrohopping
author: distrohopping (The Distro Hopper)
date: 2026-07-06T02:01:04.200650
tags: [linux, distro_migration, sysadmin]
url: https://logzly.com/distrohopping/fast-transfer-of-home-apps-settings-between-linux-distros
---


[Switching a Linux distro](/distrohopping/migrate-from-ubuntu-to-fedora-in-30-minutes-a-complete-stepbystep-guide) doesn’t have to mean losing your config, scripts, or installed apps.** In the next few minutes you’ll get a **complete, distro‑agnostic checklist** that backs up everything you need and restores it on the new system—no panic, no missing files. Follow the steps, copy the commands, and your next distro hop will feel like a single click.

## Distro‑Agnostic Checklist to Transfer Linux Home Directory Between Distributions

### 1. Backup your home folder  
Your personal data lives in `$HOME`. Create a single compressed archive you can move to any external drive or cloud storage.

```bash
tar -czvf ~/home-backup-$(date +%F).tar.gz $HOME
```

**Why it matters:** This single file contains all documents, pictures, and hidden config folders—your safety net before you wipe the disk.

### 2. Export the list of installed packages  
Each distro uses a different package manager, but the concept is identical: **save a manifest** that you can replay later.

* **APT‑based (Ubuntu, Debian, Mint)**  

  ```bash
  dpkg --get-selections > ~/pkglist.txt
  ```

* **Pacman‑based (Arch, Manjaro)**  

  ```bash
  pacman -Qqe > ~/pkglist.txt
  ```

Store `pkglist.txt` alongside your home backup; it will let you **preserve installed packages when changing Linux distro**.

### 3. Save your dotfiles  
Hidden files like `.bashrc`, `.vimrc`, and `.gitconfig` hold the bulk of your custom workflow.

```bash
mkdir -p ~/dotfiles && cp -r $HOME/.* ~/dotfiles 2>/dev/null
tar -czvf ~/dotfiles.tar.gz -C ~/dotfiles .
```

If you already track dotfiles in a Git repo, just push the latest commit instead.

### 4. Back up custom scripts and local binaries  
Anything you placed in `$HOME/bin` or `/usr/local/bin` should be saved.

```bash
cp -r $HOME/bin ~/bin-backup
tar -czvf ~/bin-backup.tar.gz -C ~/bin-backup .
```

### 5. Preserve desktop and application settings  
Most GUI apps keep their configs under `~/.config` or `~/.local`.

```bash
tar -czvf ~/config-backup.tar.gz -C $HOME/.config .
```

### 6. Restore on the new installation  

1. **Copy all archives** to the fresh system (USB, network share, etc.).  
2. **Extract the home backup** (this recreates your folder structure).

   ```bash
   tar -xzvf ~/home-backup-*.tar.gz -C /
   ```

3. **Reinstall packages** (example for APT).  

   ```bash
   sudo dpkg --set-selections < ~/pkglist.txt && sudo apt-get dselect-upgrade
   ```

4. **Unpack dotfiles** and custom scripts.

   ```bash
   tar -xzvf ~/dotfiles.tar.gz -C $HOME
   tar -xzvf ~/bin-backup.tar.gz -C $HOME
   ```

5. **Reload desktop configs** if needed.

   ```bash
   tar -xzvf ~/config-backup.tar.gz -C $HOME/.config
   ```

### 7. Tweak distro‑specific quirks  
After the bulk restore, you may need to rename a package (e.g., `vim` → `neovim`) or adjust a path that differs between distros. In most cases, everything works out‑of‑the‑box.

**Bottom line:** With a single home‑backup archive, a package manifest, and your dotfiles, you can [jump from Ubuntu to Arch, Fedora to Debian, or any other Linux combo](/distrohopping/migrate-from-ubuntu-to-fedora-in-30-minutes-a-complete-stepbystep-guide) without losing a thing. Run the checklist before you hit “install,” and your new distro will feel instantly familiar.

Enjoy the freedom to explore new Linux flavors—**happy hopping!**