Schema mapping

Fields to fields. Automatic first, manual when it matters.

See both schemas side by side, connect fields with a click, and know immediately which mappings are safe, which need a transformation and which required fields still lack a source.

01 — Mapping interface

Click a source field, then a destination field.

Eight of ten destination fields start mapped. Fix the warning, map the missing required field, then validate.

Mapped8 / 10
Warnings1
Unmapped1required · +1 optional

Click a source field, then a destination field, to connect them. Hover a field to see its mapping.

Source schema · shopify_orders
Destination schema · erp.sales_order
  • amount The source is a currency string. Add parse_decimal so the destination receives a number.
02 — How it works

Understand, suggest, review.

01

Understand

Nextra Flow reads both schemas and infers types: string, email, phone, money, date, address.

02

Suggest

Matching fields are proposed from names and types. Anything uncertain is marked for review rather than guessed.

03

Review

You approve the mapping. Each change creates a new version, so a flow can always be rolled back.

Stop building the same integration twice.

Connect your systems once.Translate your data reliably.Keep every workflow moving.