Migrating from JetBrains AI to Copilot in IntelliJ - Step by Step Guide

Making the switch from JetBrains AI to GitHub Copilot in IntelliJ IDEA doesn’t have to be disruptive. This guide walks you through every step of the migration process, from installation to configuration, ensuring you maintain your productivity while using Copilot’s strengths.

Why Consider Switching to Copilot?

GitHub Copilot offers several advantages that make it an attractive alternative:

• Broad language support including Java, Python, JavaScript, TypeScript, and hundreds more
• Tight GitHub integration for context-aware suggestions
• Extensive plugin ecosystem in IntelliJ and other JetBrains IDEs
• Flexible pricing with individual and business plans
• Strong corporate backing from Microsoft/GitHub with regular updates

JetBrains AI, while powerful, has its own ecosystem considerations. If your team has standardized on GitHub or you’re looking for more flexible licensing, Copilot might be the right choice.

Prerequisites

Before starting the migration, ensure you have:

• IntelliJ IDEA 2023.2 or later (Ultimate or Community Edition)
• A GitHub account (personal or organizational)
• An active internet connection for Copilot authentication
• Admin privileges to install plugins in your IDE

Step 1: Disable or Uninstall JetBrains AI Plugin

The first step is to remove JetBrains AI from your IntelliJ installation to avoid conflicts:

1. Open IntelliJ IDEA
2. Navigate to Settings/Preferences (Windows: Ctrl + Alt + S, Mac: Cmd + ,)
3. Select Plugins from the left sidebar
4. Search for “JetBrains AI” in the installed plugins list
5. Click Disable or Uninstall
6. Restart IntelliJ when prompted

Note: If you have multiple JetBrains IDEs, you'll need to repeat this process for each one.

Step 2: Install GitHub Copilot Plugin

Now let’s install the Copilot plugin for IntelliJ:

1. In IntelliJ, go to Settings/Preferences > Plugins
2. Click the Marketplace tab
3. Search for “GitHub Copilot”
4. Click Install
5. After installation, click Restart IDE

Once restarted, you’ll see a new Copilot icon in the bottom status bar of IntelliJ.

Step 3: Authenticate with GitHub

After installation, you need to connect Copilot to your GitHub account:

1. Click the Copilot icon in the IntelliJ status bar
2. Select Sign in to GitHub
3. A browser window will open with a device activation code
4. Copy the code from IntelliJ and paste it into the browser
5. Authorize the GitHub Copilot application
6. Return to IntelliJ - you should see “Signed in as [your username]”

If you don’t have a Copilot subscription yet, you’ll be prompted to start a free trial or subscribe.

Step 4: Configure Copilot Settings

Now let’s optimize Copilot for your Java development workflow:

Enable/Disable Copilot

You can toggle Copilot on/off easily:

• Keyboard shortcut: Alt + \ (Windows/Linux) or Option + \ (macOS)
• Via status bar: Click the Copilot icon to enable/disable inline suggestions

Adjust Suggestion Display

1. Go to Settings > Editor > GitHub Copilot
2. Configure these options:

Java-Specific Settings

For Java development, consider these additional configurations:

// Copilot works best when you provide context:
// - Use meaningful variable names
// - Add Javadoc comments
// - Keep methods focused and single-purpose

1. Go to Settings > Editor > General > Code Completion
2. Ensure Machine Learning completion is enabled
3. Set Case-sensitive completion to “None” for better suggestions

Step 5: Import JetBrains AI Custom Instructions (Optional)

If you created custom instructions in JetBrains AI, you can manually recreate them as comments in your code:

Example: Creating Context for Java Projects

// TODO: Add project context for Copilot
// Our Java project uses:
// - Spring Boot 3.2 with Java 21
// - Maven for dependency management
// - JUnit 5 for testing
// - Standard REST API patterns

Using Editor-Specific Instructions

Create a .github/copilot-instructions.md file in your project root:

# Copilot Instructions for This Project

## Code Style
- Use Java 17+ features (records, pattern matching)
- Follow Google Java Style Guide
- Prefer immutable data classes (use records)

## Testing
- Use JUnit 5 with Mockito
- Write descriptive test names
- Include arrange-act-assert comments

## API Patterns
- REST endpoints return ResponseEntity
- Use DTOs for API boundaries
- Include proper HTTP status codes

Step 6: Migrate Your Snippets

If you had custom snippets in JetBrains AI, create similar shortcuts in Copilot:

1. Go to Settings > Editor > Live Templates
2. Create new templates for frequently used patterns:

// Example: Quick test template
// Template: testu
@Test
void should$NAME$() {
    // Arrange
    $END$

    // Act

    // Assert
}

Step 7: Verify Functionality

Let’s verify everything is working correctly:

Test Inline Suggestions

1. Create a new Java class
2. Start typing a method signature:

public List<User> findUsersByEmailDomain(String domain) {
    // Copilot should suggest the implementation
}

1. Press Tab to accept suggestions

Test Chat Feature

Copilot in IntelliJ also supports chat:

1. Press Ctrl + Shift + P (Windows/Linux) or Cmd + Shift + P (macOS)
2. Ask a question like “How do I write a JUnit test for this service?”
3. Review the AI-generated response

Step 8: Compare Your Workflow

Take time to compare key aspects:

Code Generation Quality

Performance

• Suggestion speed: Copilot typically provides suggestions within 200-500ms
• Memory usage: Adds ~200MB to IDE memory footprint
• Network dependency: Requires internet for suggestions (unlike some local models)

Troubleshooting Common Issues

Copilot Not Suggesting Anything

1. Check status bar - ensure Copilot is enabled (green icon)
2. Verify you’re signed in (click Copilot icon > Account)
3. Try restarting IntelliJ
4. Check for conflicting plugins

Suggestions Are Low Quality

1. Provide more context with comments
2. Use meaningful variable and method names
3. Add docstrings to classes and methods
4. Ensure the file is saved and in a recognized project

Authentication Issues

If you see authentication errors:

1. Go to Settings > Tools > GitHub Copilot
2. Click Sign Out
3. Repeat Step 3 to sign in again

Network/Firewall Problems

If you’re behind a corporate firewall:

1. Configure proxy settings in Settings > Appearance & Behavior > System Settings > HTTP Proxy
2. Ensure ports 443 and 80 are accessible to github.com and api.github.com

Best Practices After Migration

1. Review Suggestions Carefully

Always verify Copilot suggestions before accepting:

// Don't just press Tab - review the suggestion
// Copilot might suggest insecure or inefficient code

2. Use Complementary Tools

Copilot works well with:

• IntelliJ’s built-in inspections for code quality
• SonarLint for security vulnerabilities
• lombok for reducing boilerplate

3. Provide Good Context

Copilot excels when you:

• Write descriptive Javadoc
• Use meaningful variable names
• Keep files focused and modular
• Add comments explaining complex logic

4. Train Your Team

If migrating a team:

1. Create organization-wide instructions
2. Share best practices文档
3. Set up onboarding documentation
4. Monitor adoption and gather feedback

Cost Comparison

JetBrains AI Pricing

• Bundled with JetBrains All Products Pack
• Individual tools have separate subscriptions

GitHub Copilot Pricing

Related Articles

• Copilot for JetBrains: Does It Cost Same as VSCode Version
• Free AI Alternatives to Copilot for JetBrains IDE Users 2026
• Migrating Copilot Custom Instructions to Cursor Rules.
• How to Use Copilot Agent Mode for Multi-Step Coding Tasks
• Best AI Inline Chat Features in VSCode Compared to Jetbrains

Built by theluckystrike — More at zovo.one