Migrate from Fieldy to Twenty CRM

Fieldy Customer maps directly to Twenty Company. Company name, address, phone, and domain transfer as-is. Parent-child customer hierarchies in Fieldy map to Twenty's ParentId on the Company record. Multi-location customers create separate Company records linked by a custom parent-company field.

Fieldy Contact maps to Twenty Person. Email, phone, job title, and name fields transfer directly. The Contact's link to a Customer becomes Person.companyId — the Company record must exist first, so Customers migrate before Contacts. Fieldy Contacts without a Customer link land in Twenty as Person records with no companyId.

Fieldy Job becomes Twenty Opportunity. Job name maps to Opportunity.name, job amount to Amount, scheduled date to CloseDate, and status to a StageName pick-list. Fieldy's job description and notes migrate as Opportunity body text or linked Note records. Staff assignments on jobs become Opportunity assignee links.

Fieldy job stages (New, Scheduled, In Progress, On Hold, Completed, Cancelled) map to Twenty Opportunity StageName values. Each Fieldy stage name requires a matching pick-list option pre-created in Twenty's Data Model → Opportunities → Stages. Completed jobs can map to a Closed Won or Closed Lost stage based on outcome status.

Fieldy Invoices carry billing amounts and line items. The invoice amount and status (Draft, Sent, Paid, Overdue) map to Opportunity.Amount with stage logic: Paid → Closed Won, Overdue → a custom stage or Note attachment. Invoice line-item details migrate as Note records linked to the Opportunity. Rebilling history preserved as Note entries.

Fieldy Quotes share structure with Invoices. A Quote with status 'Accepted' merges into the linked Opportunity at the quote amount. A Quote with status 'Pending' or 'Rejected' migrates as a Note on the Opportunity capturing the quote value and rejection reason rather than updating the Opportunity amount.

Fieldy Staff records (name, email, role, phone) map to Twenty Workspace Members. Email is the join key — FlitStack matches Staff email to Twenty Members invited via Settings → Members. Unmatched Staff records create Person records flagged with role in a custom field. Staff time-tracking logs migrate as Task records linked to the Person.

Fieldy stores service location as separate address fields. If the location is a Customer site, it maps to Company.streetAddress and related fields. If it's a contact's address, it maps to Person.address fields. Coordinates (latitude/longitude) from Fieldy's live tracking cannot be stored in standard Twenty address fields — these migrate to a custom text field for reference.

Fieldy custom fields on Jobs require pre-creation in Twenty as custom fields on the Opportunity object before migration. FlitStack generates the field creation list from the Fieldy schema export and can pre-create these in your Twenty workspace via API, or deliver a step-by-step guide for manual creation in Settings → Data Model.

Fieldy custom fields on Customers map to custom fields on Twenty Company. These must exist in Twenty before the Company import batch runs. If Fieldy uses custom field types (select, multi-select, date), Twenty field types must match — select fields in Fieldy create select fields with matching option values in Twenty.

Fieldy activity logs (job status changes, technician check-ins, customer communications logged on Jobs) migrate as Twenty Task records linked to the Opportunity. Each activity becomes a Task with subject, description, due date if applicable, and assignee matching the Staff who performed the action.

Fieldy job attachments (photos, signed forms, PDFs) re-upload to Twenty as Note records with file attachments on the corresponding Opportunity. File size limits follow Twenty's attachment constraints. Inline images in Fieldy notes are downloaded, rehosted as Note attachments, and linked to the Opportunity.