Migrate from Field2Base to Nutshell

Each completed Form2Base submission becomes a Nutshell Note attached to the corresponding Person or Company record. Submission region values (text, numeric, dropdown) are written as the Note body in structured format. Original submission timestamp is preserved in the Note create date. GPS coordinates captured in the form are stored as a custom field on the Note.

Each named Region in a Field2Base Form Template maps to a Nutshell custom field on the target object (Person, Company, or Lead). Region type determines Nutshell field type: Text regions → Nutshell Text, Numeric → Number, Drop-Down → Dropdown, Date → Date, Camera/Signature → Text (URL or base64 reference). We pre-create all custom fields in Nutshell before loading data.

Field2Base company records map directly to Nutshell Company records, preserving the company name, address (including street, city, state, zip, country), phone, and website fields using exact field-name matching. We recommend migrating Companies before Form Submissions so that the resulting Nutshell Company ID can be linked to each Note, ensuring referential integrity throughout the migration.

Field2Base User accounts (the office or field users who submit forms) are mapped to Nutshell Person records by email. Form Submissions carry an owner reference — that owner email is resolved to a Nutshell user. Unmatched owners are flagged before migration and assigned to a fallback Nutshell user.

Numeric Regions in Field2Base, such as measurements, quantities, or ratings, map directly to Nutshell Number custom fields. The region label, data type, and any Field2Base validation constraints (e.g., range limits) are recorded in the migration documentation, but Nutshell does not enforce those constraints automatically. By default, Nutshell numeric fields accept any numeric value, including integers and decimals, allowing downstream calculations or reporting without additional configuration.

Drop-Down Regions in Field2Base have defined option values. These are mapped one-to-one to Nutshell Dropdown custom field options. If Nutshell already has a Dropdown field with overlapping values, we merge and deduplicate during mapping. New values are added to the Nutshell field definition before migration.

Photo and signature regions in Field2Base store image data. We extract the image URL or binary, re-upload to Nutshell's file storage, and store the resulting URL as a Text custom field on the Nutshell record. Nutshell's attachment size limits apply per file.

The submittedAt timestamp on each Field2Base Form Submission is preserved as the Note create date in Nutshell. This maintains the audit trail of when field work was actually performed, separate from the migration import date. We store submittedAt as a custom datetime field on the Note for reporting continuity.

Field2Base GPS Regions capture latitude/longitude at submission time. We store coordinates as a Text custom field (e.g., '35.9297° N, 78.9486° W') on the Nutshell Note. If Field2Base stored a formatted address alongside coordinates, we attempt to map that to the Person or Company address fields.

If Field2Base DIM exports data to CSV, ODBC, or XML, we process those files directly as the migration source. Each row in the export maps to a Nutshell Note or Activity using the same region-to-custom-field mapping. DIM exports are often cleaner than live API data because they represent a consolidated data pull.

Field2Base Forms Workflow creates multi-step review and approval chains within forms. Nutshell has no equivalent — email sequences trigger on pipeline stage changes, not form submission events. We export the workflow definitions as a PDF reference document for your team to manually rebuild as Nutshell sequences or external approval tools.

Field2Base DIM (Data Integration Module), EDM (Enterprise Dispatch Module), and DUU (Data Upload Utility) configurations are third-party integration connections. These must be disconnected and rebuilt against Nutshell's API or Zapier/Make integrations. We document each active integration endpoint for your IT team to reconfigure post-migration.