# Migration and coexistence

> Move from Raycast, Tinycast or the old fork identity without losing track of your data.

There are three different migrations. Choose the one matching your current installation.

## From Raycast

Export a `.rayconfig` from Raycast, then use **Import from Raycast** in Redcast. Review the categories and any command warning before applying. The [import guide](/docs/reference/import-from-raycast) explains aliases, shortcuts, favorites, snippets, quicklinks and clipboard history.

A Raycast settings import is not a copy of its running extensions or subscription. Install extensions through Redcast's Store and connect your own AI routes.

## From Tinycast

Redcast uses a different bundle ID and can coexist with Tinycast. An upstream `.tinycast` backup can carry its supported base categories. Import it in Redcast, then configure the fork's AI, agents and voice features separately.

Give the two apps different global hotkeys while trying them side by side. Only one should own a shared physical-key remap such as Hyper at a time.

## From the old Redcast fork ID

Earlier fork builds used `com.tinycast.app.fork`. Current Redcast uses **io.redcast.app**.

On first launch under the new ID, Redcast moves the old fork's preferences, Application Support and settings-file folder to its new locations. Old directory paths remain symbolic links for rollback. Keychain items are copied lazily when first used; macOS may ask to allow the read.

The migration targets the old fork ID. It does not take over an ordinary Tinycast installation's data.

### Re-grant macOS permissions

Privacy grants cannot be moved as files. After the identity change, grant Accessibility, Microphone, Screen Recording and any other required permissions to **Redcast** again. The installer prints the relevant steps.

If macOS shows an old checked entry but the feature still fails, remove the stale entry and add the currently installed app. Test a simple paste or window action afterward.

## Moving to another Mac

Export a [full backup](/docs/reference/backup), optionally including chat history and encrypted supported secrets. Restore your project files separately. On the destination, review imported commands, adjust missing paths, sign in with ChatGPT again, and enable desired capabilities. Imported schedules are paused and imported MCP servers off.

## Names that deliberately stay unchanged

The source folder and Xcode project keep the Tinycast name. Backups still end in `.tinycast`; deep links still use `tinycast://`. These technical names do not mean the old app's storage is being used. Check the bundle ID and the paths in [privacy and data](/docs/reference/privacy).