Terminal > Migrate to Warp
Migrate to Warp
# Migrate to Warp Warp users come from every kind of terminal, editor, and AI coding tool. This section has a dedicated page for each of the most common sources, with step-by-step migration guidance, notes on what transfers automatically, and a cross-reference for the Warp features that replace what you use today. Pick the tool you're switching from: * [**Claude Code**](/getting-started/migrate-to-warp/migrate-to-warp-from-claude-code/) - use Claude Code inside Warp, or switch from Claude Code to Warp's built-in Agent Mode. Covers context, rules, and model setup. * [**Cursor**](/getting-started/migrate-to-warp/migrate-to-warp-from-cursor/) - use Warp alongside Cursor as your agent terminal, or replace Cursor entirely with Warp's built-in code editor and Agent Mode. * [**Ghostty**](/getting-started/migrate-to-warp/migrate-to-warp-from-ghostty/) - translate your Ghostty config to Warp and find equivalents for quick terminal, tabs, and GPU rendering. * [**iTerm2**](/getting-started/migrate-to-warp/migrate-to-warp-from-iterm2/) - use Warp's built-in iTerm2 importer to transfer themes, fonts, keybindings, and hotkey windows in a few clicks. * [**macOS Terminal**](/getting-started/migrate-to-warp/migrate-to-warp-from-macos-terminal/) - match your Terminal.app setup and discover the split panes, tabs, and Agent Mode features Terminal.app lacks. * [**VS Code terminal**](/getting-started/migrate-to-warp/migrate-to-warp-from-vs-code-terminal/) - use Warp alongside VS Code for a richer terminal, or replace VS Code entirely with Warp's built-in code editor. * [**Windows Terminal**](/getting-started/migrate-to-warp/migrate-to-warp-from-windows-terminal/) - map Windows Terminal profiles, PowerShell settings, and color schemes into Warp on Windows. ## Coming from something else? Warp works well for developers migrating from many other sources. If you're switching from a tool that isn't listed above - for example, Alacritty, WezTerm, Kitty, Hyper, or a Linux default like GNOME Terminal or Konsole - drop a note in our [Discord community](https://discord.gg/warpdotdev) so we can prioritize coverage.Move your settings and mental model into Warp. Pick the tool you're coming from for step-by-step guidance and Warp equivalents.
Warp users come from every kind of terminal, editor, and AI coding tool. This section has a dedicated page for each of the most common sources, with step-by-step migration guidance, notes on what transfers automatically, and a cross-reference for the Warp features that replace what you use today.
Pick the tool you’re switching from:
- Claude Code - use Claude Code inside Warp, or switch from Claude Code to Warp’s built-in Agent Mode. Covers context, rules, and model setup.
- Cursor - use Warp alongside Cursor as your agent terminal, or replace Cursor entirely with Warp’s built-in code editor and Agent Mode.
- Ghostty - translate your Ghostty config to Warp and find equivalents for quick terminal, tabs, and GPU rendering.
- iTerm2 - use Warp’s built-in iTerm2 importer to transfer themes, fonts, keybindings, and hotkey windows in a few clicks.
- macOS Terminal - match your Terminal.app setup and discover the split panes, tabs, and Agent Mode features Terminal.app lacks.
- VS Code terminal - use Warp alongside VS Code for a richer terminal, or replace VS Code entirely with Warp’s built-in code editor.
- Windows Terminal - map Windows Terminal profiles, PowerShell settings, and color schemes into Warp on Windows.
Coming from something else?
Section titled “Coming from something else?”Warp works well for developers migrating from many other sources. If you’re switching from a tool that isn’t listed above - for example, Alacritty, WezTerm, Kitty, Hyper, or a Linux default like GNOME Terminal or Konsole - drop a note in our Discord community so we can prioritize coverage.