Connect Figma

The Figma connector is the ingestion source for every project. Today we authenticate with a personal access token; OAuth is on the roadmap.

Generate a personal access token

  1. In Figma, click your avatar (top right) → Settings.
  2. Open the Security tab → Personal access tokens.
  3. Click Generate new token. Give it a name like MigrateTo and a sensible expiry.
  4. Set scopes to at least File content: Read and File metadata: Read.
  5. Copy the token immediately — Figma only shows it once.

Add the token to MigrateTo

  1. Open Settings → Integrations → Figma.
  2. Paste the token. We validate it with a test call to /v1/me and store it encrypted at rest, scoped to this workspace.
  3. Click Test connection to confirm.

What we import

  • Every page and frame, with width, height, and absolute position.
  • Every component and instance, with overrides.
  • Text content, font family, weight, size, and line height.
  • Fills, strokes, and corner radius — translated to design tokens during generation.
  • Image fills — exported on-demand and uploaded to the package as web files.

We do not import comments, prototypes, version history, or library metadata.

Refresh & re-ingest

Click Re-ingest on a file at any time. We compute a delta against the previous IR so existing mappings re-bind automatically wherever node IDs survive.

Token rotation

Rotate your token when you change roles
Figma tokens inherit your personal permissions. If you leave the team that owns a file, the token stops working — rotate to one issued by an account that still has access.

OAuth (roadmap)

Figma OAuth is on the roadmap. The benefit will be per-user consent and no token rotation when contributors change. Until then, PATs are the only supported method.

Example API call we make

GET https://api.figma.com/v1/files/:key
X-Figma-Token: <your token>
Was this page helpful?Send feedback →