How to Switch from CodeStream to GitLens

The migration, step by step

1. 1
   Prepare

   Audit how you actually use it

   List the CodeStream features your team touches weekly. Most teams use 20% of features for 80% of the work — those are the only ones the free alternative must cover.

2. 2
   Prepare

   Export your data first

   Before anything else, export everything from CodeStream. Keep the export in its original format plus any open standard offered (CSV, JSON, SVG, Markdown). Do not cancel yet.

3. 3
   Pilot

   Set up the free alternative

   Install or open GitLens and recreate one small, real project from scratch — not a toy file. This surfaces gaps while switching is still cheap.

4. 4
   Pilot

   Run a two-week pilot in parallel

   Do live work in GitLens while keeping CodeStream read-only. Note every friction point; most disappear after the first week as muscle memory adjusts.

5. 5
   Migrate

   Migrate your assets

   Move your exported files into GitLens. Where direct import is unsupported, use the open-standard export (CSV/SVG/Markdown) or a one-time conversion — then keep the originals archived.

6. 6
   Cut the cost

   Cut the subscription

   Cancel CodeStream at the end of the billing cycle (avoid losing access mid-cycle). Check the cancellation date against your renewal to dodge the next price increase.

Your destination: GitLens

Not the right fit? 2 more free alternatives