Skip to content

UX : Organization user migration process for Protocells

Summary

GitLab is implementing a two-phase customer migration strategy to move users from legacy to Protocell (Dedicated instances). The initiative includes an immediate MVC approach targeting inactive free-tier customers with automatic migration (30-day opt-out period), followed by a self-service pathway launching in Q2/Q3 2026. Both approaches prioritize seamless user experience, feature parity, and legal compliance, with customers experiencing no service disruption during the transition.

Epic reference &11839

1. Customer Migration Flow (MVC)(Target: GA Q4 2025)

Goal: Migrate inactive customers from legacy to Protocell (Dedicated instance)

User process flow:

  1. Customer Selection & Consent
  • Obtain customer consent via email notification
  • Provide clear migration timeline and benefits (If possible)
  • Collaborate with legal team for compliance requirements and best practices
  1. Opt-out Period
  • 30-day window for customer opt-out
  • Automatic migration to Protocell if no consent response received
  • Clear communication of timeline and implications
  1. Migration Execution
  • Select customers based on feature compatibility
  • Ensure no feature gaps for specific use cases
  • Maintain service continuity throughout process

2. Customer Self-Service Path (Target: Q2/Q3 2026)

Goal: Enable customer-initiated migration from legacy to Protocell via dashboard interface

User process flow:

  1. Customer Initiation
  • Opt-in migration option available in dashboard UI
  • Clear value proposition for migration benefits
  • Self-service migration request submission
  1. Suitability Assessment
  • Automated analysis of customer compatibility
  • Some evaluation criteria:
    • Feature parity requirements
    • Infrastructure setup compatibility
  1. Legal and Consent Management
  • Legal team consultation for consent capture
  • Compliance verification process
  • Documentation of customer agreement
  1. Communication and Execution
  • Email notifications for process updates
  • Migration execution with minimal disruption
  • Completion notifications to affected users
Edited by 🤖 GitLab Bot 🤖