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

# Moving Off Stardeck

> Move a domain or a Stardeck app to infrastructure you manage elsewhere.

You can move your domain, your app, or both. Moving a domain does not require moving the app, and
moving the app does not require transferring the domain registration.

## Use your domain somewhere else

If you only want the domain to point to another website or service, leave the domain registered
with Stardeck and change its DNS records:

1. Open **Organization Settings → Domains**.
2. Find the domain and click **DNS**.
3. Click **Add Record**, then add the records supplied by your new hosting provider.

The domain remains registered through Stardeck and can continue to renew there while its DNS sends
traffic to the new service. Remove or replace Stardeck's existing routing records only when you are
ready to move that traffic. If you connected a domain that is registered with another provider,
manage its DNS at that provider instead.

## Transfer your domain registration

For a domain purchased through Stardeck:

1. Open **Organization Settings → Domains**.
2. If the domain is assigned to an app, click **Unassign** first.
3. Click **Settings → Initiate Transfer**, then confirm.
4. Contact Stardeck support for the authorization code and give it to your new registrar to complete
   the transfer.

Starting a transfer unlocks the domain and disables auto-renew in Stardeck. Connected domains that
were purchased from another registrar are already managed by that registrar and do not need to be
transferred out of Stardeck.

## Move your app

Stardeck apps use [Graviton](/graviton/overview), Stardeck's architecture based on Next.js. The
repository is a Next.js app and can be adapted to run anywhere that supports Next.js, but it is not
a self-contained export of every Stardeck service.

The following platform-backed packages require Stardeck services and credentials. Replace or
re-engineer any features that use them before running independently:

| SDK                | Features you will need to replace                                                                |
| ------------------ | ------------------------------------------------------------------------------------------------ |
| `project-auth`     | Sign-in, user sessions, roles, permissions, single sign-on, and the app's user and admin screens |
| `data-store-sdk`   | Reading and writing your app's database and files stored in Stardeck Data Stores                 |
| `storage-sdk`      | Uploading, downloading, and managing files through Stardeck's legacy file storage                |
| `payments-sdk`     | Checkout, subscriptions, billing, and connections to payment providers                           |
| `email-sdk`        | Sending transactional email from your app                                                        |
| `integrations-sdk` | LINE and Slack messaging, Google Sheets sync, and Platform Identity                              |
| `scheduling-sdk`   | Scheduled and recurring jobs                                                                     |
| `document-sdk`     | Turning HTML into PDF documents                                                                  |
| `starlens`         | Extracting structured information from images, PDFs, audio, and video                            |
| `edge-sdk`         | Receipt printers, cash drawers, customer displays, and other Stardeck Edge hardware              |
| `cross-app`        | Calling API endpoints in other Stardeck apps within your organization                            |

Your repository also does not contain your hosted data, decrypted secrets, domain registration, or
dashboard configuration. Move each dependency your app uses and configure its replacement on the
new host. See [The SDKs](/graviton/sdks) for the full capability map.

## Move your Data Store data

Cloning the repository does not copy your Data Stores. Export and import the data separately before
switching off the Stardeck-hosted app.

For a database store:

1. Open **Dashboard → Data Stores**, then select the store and the branch you want to move.
2. Open a table and click **Export**.
3. Choose CSV or TSV, include all columns, and download the export.
4. Repeat for every table and every branch you need, then import the files into your new database.

Each export contains at most 100,000 rows. For a larger table, use non-overlapping filters and
export it in batches. CSV and TSV files contain table rows, not database constraints, indexes,
relationships, or migrations. Recreate that structure separately using the schema shown in the
Data Store editor; older apps may also have migration files in their repository.

For a storage store, open it from **Dashboard → Data Stores** and download the files from its file
browser. A database export only includes references to files stored in a storage store, not the file
contents, so move those files separately and update their references in the new system.

Keep the original Data Stores until you have imported the data and verified the new app. See
[Data Stores](/data-stores/overview) for more about database and storage stores.

## Get the code

1. Open the app in Stardeck and go to **App Settings → Repository**.
2. Under **GitHub Repository Access**, click **Add GitHub User**.
3. Enter your GitHub username, grant the access level you need, and click **Add Collaborator**.
4. Accept the private-repository invitation from GitHub.
5. Clone the repository from GitHub.

The clone gives you the app's code and Git history. From there, you can change the code, replace its
Stardeck dependencies, and deploy it on infrastructure you control. For access details and
troubleshooting, see [Managing GitHub Repository Access](/github-access).

## Need help moving off Stardeck?

Stardeck offers a migration service for a one-time charge. Contact your account executive or email
[support@stardeck.ai](mailto:support@stardeck.ai) for help.