Migrate your Field2Base data

Form templates are the top-level container defining form structure. We export the full template definition including all Region layouts, validation rules, drop-down options, and required-field flags. Templates are stable JSON structures exportable via the portal's Forms section.

Regions are the field-level definitions within a form template — including Text, Numeric, Date, Drop-Down, Checkbox, Camera, GPS, and Signature types. We preserve the complete Region configuration including field labels, data types, default values, and conditional visibility rules.

Submitted forms are the primary data record containing all captured field values, timestamps, GPS coordinates, photos, and signatures. We export full submission records with their parent template linkage. Offline-draft submissions are flagged and cleaned before ingestion.

Users, role definitions, and permission sets are managed through the Admin Portal. We export user accounts, role names, and access scopes. Role semantics differ significantly between tiers — Essentials supports basic user management while Small Business and Enterprise add granular permissions — so we map each role to the destination's equivalent access model.

Workflows define the review-and-approval chain for submitted forms — typically a one-step review by an authorized reviewer. Workflow definitions include step order, approver assignments, and audit-trail settings. We export workflow definitions and map them to the destination's routing or approval logic.

Work orders are pre-filled form templates sent to field workers with customer and job context. Work order numbering is automated via Field2Base's built-in sequence fields. We export work order records and map the pre-fill field values to the destination's job or task object.

Submitted forms store attachments (photos, signatures, PDFs) linked to each record. We export binary attachments and associate them with the corresponding submitted form record in the destination system. Large photo galleries require chunked download handling.

E-Mail Templates define the message bodies and subject lines used in form notifications and workflow routing. Template variables and merge-field syntax vary from standard HTML email templates, so we map the content to the destination's notification template model.

Company-level configuration including branding, logo, and portal preferences is stored in the Admin Portal. These settings are configuration data rather than operational records, so we map them to the destination's org or account settings object.

Incomplete form submissions saved locally on mobile devices are not synced to the cloud until connectivity is restored. Drafts on decommissioned devices or devices not re-synced before migration are not accessible via API or portal export. We recommend forcing a device sync before migration cutover to capture pending drafts.