Dundie·Migration guideSample

This is a real guide, generated for an example user. Yours is built from a short interview about how you actually work — your saved prompts, your projects, your do-not-break workflows. Free during beta.

Sample · migration guide

How to move from Cursor to GitHub Copilot.

A step-by-step playbook to move Cursor workflows into GitHub Copilot — copy-ready, checkable, and checked against each tool’s own docs.

Prepared for: An example 3-person marketing team
Sources: 10 verified sources

Start your Cursor → GitHub Copilot migration See what carries over

workflows covered

~105min

to switch

to confirm

Early

confidence

completed

7 steps, 3 paste-ready assets, 10 to confirm in GitHub Copilot, about 105 minutes.

Workflows being migrated

AI multi-file refactors in the editor
Terminal command help

Setup steps

Work through these in order. Check each off as you go; your progress is saved on this device.

Install the GitHub Copilot extension in VS CodeConfirm in GitHub CopilotConfirmed in GitHub Copilot
Cursor is a standalone IDE; Copilot is a plugin. In VS Code, open Extensions (Marketplace), install "GitHub Copilot" and "GitHub Copilot Chat", then sign in with your GitHub account. VS Code and Git are already in your stack, so no new IDE needed.
Ide foundation
Enable inline completion + Next Edit SuggestionsConfirm in GitHub CopilotConfirmed in GitHub Copilot
Ghost-text completion is on by default — Tab to accept. To approximate Cursor Tab's chained cross-file edits, enable "GitHub Copilot: Next Edit Suggestions" (NES) in VS Code settings; Tab through suggested next edits via the gutter arrow. Note: the completion-model picker (Settings > GitHub Copilot > Completions) only affects ghost text, not NES.

A few things to confirm

We flag these up front so nothing surprises you — a short list to double-check in GitHub Copilot as you go.

May be incomplete

This guide may be incomplete — the generation was cut off. Double-check the steps against your current tool before relying on them.

10 items are flagged to confirm in GitHub Copilot — check the menu paths and field names as you go.

Paste-ready assets

Workflows from Cursor, rewritten to paste straight into GitHub Copilot.

project.github/copilot-instructions.md (ported from .cursor/rules)AI multi-file refactors in the editorConfirm in GitHub CopilotConfirmed in GitHub Copilot

From Cursor

.cursor/rules/*.mdc + saved Composer prompts

Into GitHub Copilot

# Copilot Repo Instructions

## Refactor conventions
- When renaming a symbol, update ALL references across the workspace, not just the open file.
- For API migrations, thread new parameters through every call site and update type signatures.
- Preserve existing import ordering and formatting; do not reformat untouched lines.
- After any multi-file edit, list the files changed and summarize the diff terse.

## Style
- Terse responses. No preamble. Show the plan, then the diffs.

## Context
- Treat the whole repo as in scope for refactors (#codebase / @workspace).
- Prefer Edit mode for scoped changes; use Agent mode for cross-cutting refactors that need terminal/test runs.

Same-day walkthrough

# Cursor → GitHub Copilot: Same-Day Migration Walkthrough You can be productive in Copilot within ~45–60 minutes. Follow this sequence: ## Phase 1 — Install & enable (~10 min) 1. **Install the GitHub Copilot extension** in VS Code (Step 1). Sign in with the GitHub account that carries your Copilot seat. 2. **Enable inline completion + Next Edit Suggestions** (Step 2). This is your closest analog to Cursor's tab-autocomplete flow. *Reminder:* sign-in and seat check first — nothing else works until the extension is authenticated. ## Phase 2 — Learn the interfaces (~10 min) 3. **Open the Chat panel and explore Edit/Agent modes** (Step 3). Spend a few minutes clicking between modes so you know which one you're in before you start editing. 4. **Try Agent mode on a small coordinated change** (Step 4) before trusting it on anything large. *Reminder:* Edit mode = scoped/inline; Agent mode = multi-file, autonomous. Confirm the mode indicator before submitting. ## Phase 3 — Port your repo context (~15 min) 5. **Migrate `.cursor/rules` → `.github/copilot-instructions.md`** (Step 5). Paste in the ported project file translation, then commit it to the repo so the whole team inherits it. 6. Reload the window and ask Chat a question that should trigger a rule, to confirm the instructions are being picked up. *Reminder:* the file lives at the repo root under `.github/`. Wrong path = silently ignored. ## Phase 4 — Terminal + plan check (~10 min) 7. **Install the Copilot CLI** for terminal command help (Step 6). Use the paste-ready "Terminal command help" prompt to smoke-test it. 8. **Confirm plan/model expectations** (Step 7). Note that Copilot does **not** support BYOK — you're limited to the models your plan exposes. If your Cursor workflow depended on a specific external model/key, flag that now. ## Paste-ready translations to load - **Project:** `.github/copilot-instructions.md` (use during Phase 3, Step 5) - **Prompt:** Multi-file refactor → run in **Agent mode** (Phase 2, Step 4) - **Prompt:** Terminal command help → run in **Copilot CLI** (Phase 4, Step 7) ## Key gotchas - **No BYOK:** verify model availability against your plan before relying on any specific model. - **Mode confusion:** Cursor's single chat differs from Copilot's Edit vs Agent split — always check the active mode. - **Instruction file path:** `.github/copilot-instructions.md` must be at repo root and committed to take effect.

Your turn

This sample was built for an example user. Yours gets built around how you work.

A 15–25 minute interview captures your workflows, then the guide is generated for you — same structure, your prompts, your projects, your gotchas. Nothing in your stack is changed or cancelled by any of it.

Start your Cursor → GitHub Copilot migration See what carries over