---
title: "Migrate an Integration from one Event Orchestration to another"
method: POST
path: "/event_orchestrations/{id}/integrations/migration"
tags: ["Event Orchestrations"]
---

# Migrate an Integration from one Event Orchestration to another

`POST /event_orchestrations/{id}/integrations/migration`

Move an Integration and its Routing Key from the Event Orchestration specified in the request payload, to the Event Orchestration specified in the request URL.

Any future events sent to this Integration's Routing Key will be processed by this Event Orchestration's Rules.

For more information see the [API Concepts Document](../../api-reference/a47605517c19a-api-concepts#event-orchestrations)

Scoped OAuth requires: `event_orchestrations.write`

## Path parameters

- `id` string, required

## Headers

- `Accept` string, required
- `Content-Type` 'application/json', required

## Request body

- object
  - `source_id` string, required — The ID of the Event Orchestration you'll be moving the Integration away from
  - `source_type` 'orchestration', required — The type of of the `source_id` object
  - `integration_id` string, required — The ID of the Integration you'll be moving

## Response `200`

The Integration that was migrated

- object
  - `integrations` OrchestrationIntegration[]
    - `id` string — ID of the Integration.
    - `label` string — Name of the Integration.
    - `parameters` object
      - `routing_key` string — Routing Key used to send Events to this Orchestration
      - `type` string
  - `total` Total — unresolved $ref

## Other responses

- `400` — Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work.
- `401` — Caller did not supply credentials or did not provide the correct credentials. If you are using an API key, it may be invalid or your Authorization header may be malformed.
- `403` — Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action.
- `404` — The requested resource was not found.
- `405` — The request was received and recognized by the server, but its HTTP method was rejected for the requested resource.
- `409` — The request conflicts with the current state of the server.

---

[API](https://skmtc.net/pagerduty/apis/rest-api.md) · [All operations](https://skmtc.net/pagerduty/apis/rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pagerduty/rest-api/revisions/b679a8f3f02c/schema)