Skip to content
Developers

Migrate to Synq.
Drop-in, route by route.

Every guide opens with a one-page mapping table, walks the dual-issuer pattern (run both for a sprint), and ends with a before/after file diff. Replace one route at a time; ship in a week.

Pick your starting point

Where are you migrating from?

The shape of a migration

Same pattern, different starting point

1

Map your provider config

Each guide opens with a side-by-side: the old config (env vars, provider definitions, callback URLs) and the equivalent Brand + Connection setup in Synq.

2

Run both issuers in parallel

Dual-issuer middleware accepts tokens from either the old issuer or Synq for a configurable window. New sign-ins land in Synq; existing sessions keep working.

3

Swap one route at a time

Once dual-issuer is in place, you rewrite per-route. Swap the auth check, deploy, watch the audit log, move on. No big-bang cutover.

Stop maintaining auth code.

Pick the guide for your current stack. Map your config, run dual-issuer for a sprint, swap routes. Ship in a week.