From Azure to GitLab: Safely Migrating Active Development Work During a Repository Migration

Introduction Repository migrations are often perceived as straightforward infrastructure activities. In reality, developers frequently face a more complicated challenge: "What happens to the work that is already in progress?" I recently faced a situation where an ongoing feature was being developed in a repository originally hosted in one Git platform while the organization migrated to another platform. The challenge was not simply moving code. The challenge was safely migrating active work without: Losing commits Pushing to deprecated branches Creating merge conflicts Breaking the development workflow Introducing confusion among team members This article summarizes the lessons learned and the approach that ensured a smooth transition. The Situation The development team received guidance similar to: Stop pushing to branches originally created in the old repository platform. Create new branches in the new platform. Verify branch history before using migrated branches. Use new authentication credentials for the new platform. At first glance the instructions seemed simple. However, there was already: Ongoing feature development Local commits Existing branch history Local test configurations New authentication requirements The biggest question became: "How can existing work be moved safely without starting over?" Step 1: Verify the Current State Before making any migration-related changes, it is important to understand exactly where the work exists. A few simple checks help answer: Which branch am I on? Are there uncommitted files? Have commits already been created? Which remote repository am I connected to? Understanding the current state prevents accidental mistakes later. One of the most valuable lessons was: Never assume your local branch matches the remote branch. Verify first. Act second. Step 2: Separate Real Changes from Local Testing In most projects there are usually two types of modifications: Functional Changes Actual feature development or defect fixes inte