Migrating from Pipefy without a freeze week

The reason migrations get postponed forever is the freeze: “nobody touch anything while we move.” BRAND_NAME’s importer is built so you don’t need one.

Imports run in the background

You point the Pipefy importer at a pipe and it runs as a background job. Large pipes don’t block the UI and don’t block your team — you keep working in the old tool until you’re ready to cut over.

Owner-only, by design

Imports are owner-only. Migrating a workflow rewrites structure — phases, fields, rules — so it isn’t something a member triggers by accident from a settings screen.

What comes across

Pipe structure and cards map onto BRAND_NAME’s model: phases become phases, fields map to the closest of the 16 field types, and cards land in the right phase. Once it’s in, you get the things Pipefy charges extra for — SLA calendars, formula fields, cross-field validation — on the same data.

A practical sequence

1. Import into a fresh pipe and review the field mapping.
2. Rebuild SLAs and validation rules (this is where you tighten the process, not just copy it).
3. Run both in parallel for a few days.
4. Cut over and archive the old board.