Data transfer
The Transfer tab defines named data transfer profiles for a record type. A profile controls which fields move, how records are matched, and how references are represented — so imports and exports stay predictable and governed.
Profile settings
Section titled “Profile settings”- Direction — import, export, or both.
- Format — JSON is the implemented format; CSV ZIP export exists for tabular delivery.
- Identity mode — how incoming rows match existing records: by record id, by record number, or by a chosen field value.
- Fields — which fields participate, with per-field import and export participation.
- Import mode — create only, update only, or create-or-update.
- Table handling — how child table rows are applied: replace all rows or upsert by row id.
- Reference resolvers — how Reference and Inverse reference fields are represented in the payload: by referenced record id (default), by record number, or by one selected field of the target.
Export profiles appear in the Data Explorer export menus; import profiles appear in its import flow. Imports run as a plan-then-apply flow, so changes can be reviewed before they are applied.
Records, not configuration
Section titled “Records, not configuration”Data transfer moves record data. Moving the entity configuration itself (the definition with its fields and settings) is a separate definition export/import feature available from the entity definition header menu.
Data transfer in the API
Section titled “Data transfer in the API”Integrations use the Entity Data Transfer operations: list export and import profiles, export JSON or CSV ZIP, fetch an import template, and run import plan and apply steps.
Where to go next
Section titled “Where to go next”- Read Import and export for the user-facing workflow.
- Read Fields and schema for the field types that profiles move.