Migrating from the legacy integration framework

Use this section when your integration still defines its data fields through Template Groups.

🚧
Note
In the legacy framework, a Template Group defines both integration fields and Oneflow fields. Oneflow provides a synchronized legacy Blueprint and Playbook for an existing Template Group, allowing existing integrations to continue working.
Migrating that legacy Blueprint to an independently managed Blueprint is a one-way, account-specific operation.

Choose your path

Your situation	Recommended next step
Your integration still works through Template Group endpoints	Continue using the Template Group endpoints and synchronized legacy objects.
Another integration needs to share mapped values	Review the synchronized Playbook and connect or map the additional Blueprint.
You want to manage integration fields through Blueprint endpoints	Plan and test the one-way migration for each customer account.
You are building a new integration	Define the integration schema with a Blueprint and use a Playbook for shared Oneflow fields.

Migration resources

Migration guide explains compatibility behavior, API changes, testing, and rollout.
Quick start: Blueprints and Playbooks shows how to set up and test an integration.
Core building blocks explains the object and responsibility split.