> For the complete documentation index, see [llms.txt](https://docs.flxbl.io/flxbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flxbl.io/flxbl/codev/migrating/migrating-to-codev/from-buildkite.md).

# From Buildkite

The approach to moving a Buildkite pipeline onto codev is the same as any other CI: connect the repository to sfp server, then hand build-on-merge, releases, pools, and validation to the server one at a time. Read [Migrating to codev](/flxbl/codev/migrating/migrating-to-codev.md) for that end-to-end flow.

A Buildkite-specific walkthrough — mapping your pipeline steps and agent configuration onto codev, the way [From GitHub Actions](/flxbl/codev/migrating/migrating-to-codev/from-github-actions.md) maps a GitHub Actions workflow — is in progress.

In the meantime, the CI-agnostic parts apply directly:

* **Connect the repository.** Onboarding registers the webhooks the server listens on, so a merge notifies codev without a Buildkite trigger. See [Step 1](/flxbl/codev/migrating/migrating-to-codev.md#step-1-connect-the-repository-to-sfp-server) and the [source control](/flxbl/codev/integrations/source-control.md) integration for your host.
* **Hand over build-on-merge.** Turn it on per domain from **Workflow Settings**; the server builds on its own image, so there is no sfp image to pin in your Buildkite agents. See [Step 2](/flxbl/codev/migrating/migrating-to-codev.md#step-2-turn-on-server-managed-builds-gradually).
* **Keep the rest of your pipeline running** until you move each part — provided those steps run [sfp-pro](https://docs.flxbl.io/flxbl/sfp) on the same release as the server (see [While you still run some builds yourself](/flxbl/codev/migrating/migrating-to-codev.md#while-you-still-run-some-builds-yourself)).

<figure><img src="/files/KdKLqpwUcV28fRc1qnDP" alt="Build Workflow Settings dialog with the Enable server builds toggle, branch exclusions, and domain build scope"><figcaption><p>The handover control is the same whatever CI you come from: turn on server builds per branch and per domain from Workflow Settings, while your Buildkite pipeline keeps running everything else.</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flxbl.io/flxbl/codev/migrating/migrating-to-codev/from-buildkite.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.