Migrating to a New Flipper Zero: Backup, Restore, and Firmware Wipe Recovery

Whether you're replacing a Flipper Zero after hardware failure, sending a unit in for warranty repair, or just recovering from a firmware flash that went sideways, the actual data you care about — saved NFC/RFID captures, Sub-GHz recordings, IR remote libraries, and installed apps — lives in a specific, well-defined place, and a full recovery is straightforward once you know where to look. This guide covers backing up before something goes wrong, migrating everything to a new or freshly-wiped device, and recovering from a bad flash.

What Actually Needs Backing Up

Almost everything you'd care about losing lives on the Flipper's microSD card, not in the device's internal flash: Sub-GHz captures, NFC/RFID dumps, IR remote files, iButton reads, BadUSB scripts, and any installed FAP apps you've side-loaded all live in folders on the SD card. The device's internal flash mainly holds firmware and a small amount of settings/configuration state. Practically, this means the single most important backup habit is simply not losing the SD card itself and keeping a copy of its contents on a computer — everything else is close to secondary.

Backing Up via qFlipper

qFlipper (the official desktop companion app) has a dedicated backup function that captures both the internal flash filesystem and lets you separately copy the SD card contents. Connect the Flipper via USB, open qFlipper, and use the file manager view to browse and copy the full folder structure to your computer — treat this as the source of truth for your device's data. Do this before any firmware update, not just when something's already gone wrong; a firmware flash is one of the few operations that can, in rare cases, disrupt internal flash contents even though it's not supposed to touch the SD card.

The Simplest Migration Path: Just Move the SD Card

Because the vast majority of your actual content lives on the SD card, the fastest and most reliable way to migrate to a new Flipper Zero is often simply moving the physical microSD card from the old device to the new one, powering on, and letting the new device read the existing folder structure. This works cleanly between devices running the same or compatible firmware (stock-to-stock, or the same custom firmware on both), and avoids re-copying anything. If the new device is running a different firmware than the old one (for example, moving from stock to Momentum, or between different custom firmware forks), check that firmware's documentation for any folder-structure migration notes before assuming a straight swap will work — most custom firmwares maintain compatible SD layouts, but it's worth a quick check rather than an assumption.

Recovering from a Bad Firmware Flash

A Flipper that won't boot normally after a firmware flash almost always still responds to DFU (device firmware update) mode, which is a lower-level recovery mode independent of whatever's currently (or isn't) running on the main firmware. Hold the Back and Down buttons together to force the device into DFU mode (the screen will typically stay blank, which is expected), then use qFlipper's firmware installation function to reflash a known-good firmware build. This recovers the vast majority of "bricked after a bad flash" situations, since DFU mode lives below the application firmware layer and isn't affected by a failed or corrupted firmware install.

Migration Checklist

StepNotes Full qFlipper backup of the old device before touching anythingCheap insurance even if you plan to just swap the SD card Copy SD card contents to a computer as a second backupProtects against a lost or corrupted SD card, independent of device backup Confirm new device's firmware matches or is compatible with old device'sPrevents folder-structure mismatches on custom firmware Move the SD card (or restore its contents to a new card) into the new deviceFastest path for same/compatible firmware Reinstall any side-loaded FAP apps not bundled with the target firmwareSome apps are firmware-bundled and reappear automatically; others need manual reinstall Re-pair Bluetooth (mobile app, BLE peripherals) on the new deviceBluetooth pairing is tied to the specific device's radio, not the SD card

What Doesn't Transfer Automatically

Bluetooth pairings (to the Flipper mobile app or other BLE peripherals) are tied to the specific hardware radio of each device and need to be re-paired after migration — this is the item people most often forget, only noticing when the mobile app can't find their "new" Flipper. Any settings stored purely in internal flash rather than on the SD card (some device-specific configuration) also won't carry over with just an SD card swap; a full qFlipper backup-and-restore covers this if it matters to your setup, though for most users it's a minor inconvenience of re-toggling a few settings rather than lost data.

The practical takeaway is that Flipper Zero migration is far less fragile than it might seem, precisely because the device was designed with an SD-card-centric data model. Keep the habit of a periodic qFlipper backup, know where DFU mode is if a flash goes wrong, and swapping hardware — whether planned or forced by a failure — is a five-minute task rather than a data-loss event.

Related Guides

Loading_