timetobail
My stack

Playbook for makers · Forced move · free while in beta

Act

GitLab 20.0 removes compliance pipelines (May 20, 2027)

Readers can stay on GitLab: they change a setting or plan. Help the ones who would rather leave.

214 days left · May 20, 2027 · Public page

Low switching pressure29/100

An estimate from the deadline, cost, discussion and need to move. It is not a product rating.

What goes into it

Confidence: medium.

deadline8/30
money14/25
attention0/25
audience0/12
force7/8
  • Hard deadline in 214 days.
  • The change is forced: it reaches users even if they wait.

  1. 1 Related discussions

    Only threads tied to this event that talk about leaving, moving or prices. Saved, not live. Check the date and read the thread before replying.

    No live threads yet.

  2. 2 What people ask

    No common questions yet.

  3. 3 Reply templates

    Answer the question first. Link only if it helps. Always keep the disclosure line. Never post the same text twice.

    Helpful first
    Sorry you have to deal with this. You can stay on GitLab. Here is what to change before May 20, 2027:

1. List your frameworks. Find each compliance framework that has a compliance pipeline set.
2. Use the migrate button. Open the framework and select Migrate pipeline to a policy.
3. Test the policy. Run a pipeline in a test project and check that the required jobs still run.

If they would rather leave, describe a verified way <your product> can help: <your link>
[Disclosure: I build <your product>.]
    Short answer
    You have until May 20, 2027. You can stay on GitLab. First: list your frameworks. Then use the migrate button.
Happy to help if you get stuck.
[Disclosure: I build <your product>.]

  4. 4 Switch-page builder

    Create a draft “Switch from GitLab” page. Add your product, review every claim, then copy HTML or Markdown. Your product claims need your own evidence.

    • Add your product name to replace “Your product”.
    Preview

    Switch from GitLab to Your product

    GitLab compliance pipelines: a change is due by May 20. You can stay on GitLab. If you would rather leave, here is how to move to Your product.

    What changes at GitLab

    GitLab deprecated compliance pipelines in GitLab 17.3. They are set to be removed in GitLab 20.0, planned for May 20, 2027. GitLab asks you to move each one to a pipeline execution policy. The framework page has a button that does the move.

    • GitLab 20.0 release (planned): May 20, 2027 (GitLab)
    • Removed in: GitLab 20.0 (GitLab)
    • Deprecated in: GitLab 17.3 (GitLab)
    • Replacement: Pipeline execution policy type (GitLab)
    • Breaking change: Yes (GitLab)
    • How to move: In the compliance framework, select Migrate pipeline to a policy in the banner (GitLab)
    • Before you turn on policies: Move the compliance pipeline first; do not run both in the same project (GitLab)
    • GitLab.com: Deprecated features can be removed at any time in the month before the release (GitLab)
    • Compliance frameworks with a compliance pipeline: Must move to a policy before GitLab 20.0 (GitLab)

    You can stay on GitLab if you make the change. This page is for people who would rather leave.

    What Your product gives you

    Write two or three short lines here. Say what Your product does, who it is for, and what it costs. Use only facts you can show.

    How to move from GitLab to Your product

    1. Save what you need from GitLab. Keep a copy before you cancel anything.
    2. Import into Your product. Say which files you accept and how long an import takes.

    Tell readers the key date: May 20, 2027.

    Questions people ask

    If Your product has a direct answer to one of these, add it here. Keep it short and true.

    How to help new users settle in

    Send one short email. Say what changed, where to find you now, and what they need to do. Put the most important line first.

    If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

    Sources

  5. 5 Search ideas to validate

    suggested, not measured Phrases people may search when a tool changes like this. We have no search volume data for them.

    • gitlab compliance pipelines
    • gitlab alternative
    • gitlab alternatives
    • gitlab export
    • how to leave gitlab
    • switch from gitlab
    • gitlab migration
    • gitlab migration 2027