How to Migrate GitHub Copilot License From Personal to Organization
🔍 WiseChecker

How to Migrate GitHub Copilot License From Personal to Organization

You have a personal GitHub Copilot subscription and your company now wants you to use a Copilot license managed by your organization. Moving from a personal plan to an organization-managed plan requires specific steps to avoid double billing and service interruptions. This article explains the exact migration process, including how to cancel your personal subscription and accept the organization invitation. It also covers common pitfalls like overlapping billing cycles and what to do if the organization seat does not activate immediately.

Key Takeaways: Migrating Your Copilot License to an Organization

  • GitHub.com > Settings > Billing and plans > Plans and usage: Cancel your personal Copilot subscription to stop future charges.
  • GitHub.com > Your organizations > Organization settings > Copilot: Organization admin must assign you a Copilot seat before you can start using it.
  • Email invitation from GitHub: Accept the organization’s Copilot invitation within 7 days to activate the new license without service gaps.

Understanding Personal vs Organization Copilot Licenses

A personal GitHub Copilot subscription is billed directly to you through your GitHub account. An organization license is paid for by the organization and assigned to individual members. When you migrate, you must cancel your personal plan before the next billing date to avoid being charged for both subscriptions. The organization admin controls seat assignments, not you. After cancellation, your Copilot access continues until the end of your current billing period. During this window, the organization must invite you and you must accept the invitation.

Prerequisites for Migration

Before you start, confirm these items:

  • You have a personal GitHub Copilot subscription active.
  • You are a member of the target GitHub organization.
  • The organization has an active GitHub Copilot for Business plan.
  • You can access your GitHub account settings and billing page.

Steps to Cancel Personal Copilot and Accept Organization Invitation

This process has two phases: first cancel your personal subscription, then accept the organization seat. Do not skip the cancellation step or you will be double billed.

  1. Cancel your personal Copilot subscription
    Go to GitHub.com and click your profile picture in the top-right corner. Select Settings from the dropdown. In the left sidebar, click Billing and plans, then Plans and usage. Scroll to GitHub Copilot and click Cancel. Confirm the cancellation in the dialog that appears. Your personal subscription will remain active until the end of the current billing period.
  2. Notify your organization admin
    After cancellation, send a message to your GitHub organization owner or billing manager. Ask them to assign a Copilot seat to your account. The admin does this in Organization settings under Copilot > Seat management.
  3. Check your email for the invitation
    GitHub sends an email invitation to the address associated with your GitHub account. The subject line reads: “You have been granted a GitHub Copilot seat by [Organization Name].” The invitation expires after 7 days.
  4. Accept the organization Copilot invitation
    Open the email and click Accept invitation. You are redirected to GitHub. A confirmation page displays the organization name and the start date of your new Copilot access. Click Join organization Copilot to finalize.
  5. Verify your active license
    Go to GitHub.com > Settings > Billing and plans > Plans and usage. Under GitHub Copilot, the entry should show the organization name as the billing entity. The personal subscription line should show as canceled.

If You Cannot Find the Invitation Email

Ask the organization admin to resend the invitation from the Copilot seat management page. Also check your spam folder. If you use email forwarding, confirm the invitation was not blocked by a filter.

Common Issues After License Migration

Copilot Stops Working Before Organization Seat Activates

Your personal subscription ends on the last day of the billing period. If the organization seat is not assigned before that date, Copilot stops working. To avoid this, schedule the migration so the organization seat activates at least 2 days before your personal plan expires. The admin can assign the seat at any time, even before your personal plan ends. Both licenses can overlap for a few days without conflict.

Double Billing for One Month

If you cancel your personal plan after the new billing cycle starts, you are charged for that month. The organization also pays for your seat. To prevent double billing, cancel your personal plan at least 3 days before the next billing date. GitHub does not issue refunds for partial months on personal subscriptions.

Organization Seat Shows as Pending

After the admin assigns a seat, it may show as Pending until you accept the invitation. If the status stays Pending for more than 24 hours, ask the admin to remove and reassign the seat. Then check your email again for a new invitation.

Copilot Features Are Different Under Organization License

An organization plan may enforce policies that your personal plan did not. For example, the admin can disable Copilot Chat for certain repositories or require code review before suggestions are used. You cannot override these settings. Review your organization’s Copilot policy document if features like chat or inline suggestions seem restricted.

Personal Copilot vs Organization Copilot: Key Differences

Item Personal Copilot Organization Copilot
Billing Your credit card Organization payment method
Seat assignment Automatic with subscription Admin assigns individual seats
Policy control None Admin sets usage policies
Data privacy No code audit by default Organization may audit code suggestions
Cancel process Self-service in billing settings Admin removes seat

You can now successfully migrate your GitHub Copilot license from a personal subscription to an organization-managed seat. Start by canceling your personal plan in GitHub billing settings to avoid extra charges. Then accept the invitation from your organization admin. After the migration, verify the active license in your billing page and test Copilot in your editor. If you need to switch back to a personal plan later, you can purchase a new personal subscription at any time and the organization admin can remove your seat.