> ## Documentation Index
> Fetch the complete documentation index at: https://docs.heyniblet.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate a supported Tidbyt Gen 1

> Install Niblet firmware and import compatible public app identities without moving secrets.

Niblet can extend the useful life of supported first-generation Tidbyt hardware. The browser flow installs a board-specific image, provisions Niblet, and can match public app identities against the compatible catalog.

## Before you begin

* Use desktop Chrome or Edge with Web Serial support.
* Connect directly with a data-capable USB-C cable and avoid hubs.
* Keep the display powered until write verification finishes.
* Keep the legacy device ID and API token nearby if you want to preview imports.

<Steps>
  <Step title="Install Niblet firmware">
    Open [the installer](https://www.heyniblet.com/install), choose the Gen 1 path, connect the serial device, and install the signed image offered for the detected chip family.
  </Step>

  <Step title="Provision the display">
    Assign a room, join the new temporary setup network, and send Wi-Fi plus the one-time private feed through the local setup page.
  </Step>

  <Step title="Preview compatible apps">
    Niblet reads public installation identities from the legacy API and matches them against the current catalog.
  </Step>

  <Step title="Review before enabling">
    Imports are created disabled. Re-enter configuration, reconnect credentials and OAuth providers, then enable each app intentionally.
  </Step>
</Steps>

## What does not migrate

The legacy API does not expose installation configuration. Passwords, API keys, OAuth grants, pushed images, deleted apps, and catalog misses are never copied silently. The migration result calls out every item that needs attention.

<Note>
  Tidbyt is a trademark of its respective owner. Niblet is an independent project and is not affiliated with or endorsed by Tidbyt.
</Note>