Migrate from FieldPro to Twenty CRM

FieldPro Outlet maps directly to Twenty Company. The Outlet name becomes the Company name, domain/website transfers to the website field, and address fields map as free-text address fields on the Company record. Outlet type or category stored as a custom select field in Twenty since no native Industry or Type field exists.

FieldPro Contact maps to Twenty People. Every Contact in FieldPro is linked to one or more Outlets — the primary (most recently modified) Outlet becomes the CompanyId link in Twenty. Secondary Outlet associations migrate as custom relation fields or notes for reference.

FieldPro Agent records map to Twenty Workspace Members. Agents must be invited to Twenty and accept their invitation before migration runs, otherwise owner references on records cannot resolve. Unmatched agents are flagged and assigned to a fallback member during migration.

FieldPro Visit records — tracking when an agent visited an outlet — map to Twenty Tasks. The Task gets linked to the corresponding People and Company records. Visit timestamps, GPS coordinates, and visit outcome/status transfer as custom fields on the Task since Twenty's standard Task object has limited custom fields.

Visit notes and comments from FieldPro migrate as Twenty Notes attached to the relevant People and Company records. This preserves the narrative context of each visit in a format that Twenty's interface surfaces alongside other record activity. Notes are timestamped and appear in the activity timeline, maintaining the chronological history of interactions for each account.

FieldPro Orders (products ordered through the platform) map to Twenty Opportunities. The Order total amount becomes the Opportunity amount, the outlet maps to the associated Company, and the Order status (pending, fulfilled, cancelled) maps to Opportunity stage values via value mapping. Order line items are stored as a custom field or note.

FieldPro Product catalog has no direct Twenty CRM equivalent. Products migrate as a custom object in Twenty (Product or Item) created in Settings → Data Model before import. Fields: product name, SKU, price, description. Products are then linked to Opportunities via a custom relation field.

FieldPro sales targets per agent or outlet have no equivalent in Twenty's standard model. These migrate as a custom Target object with fields for period, target_amount, and actual_amount, linked to the relevant Agent (WorkspaceMember) or Company via custom relation fields.

Every FieldPro custom field must be pre-created in Twenty's Settings → Data Model on the corresponding object before import runs. Twenty's import tool creates records, not fields — attempting to import into a non-existent custom field causes an error and the row is skipped.

FieldPro captures latitude and longitude on Outlet records. Twenty has no native geolocation field on the Company object. The coordinates migrate as two custom number fields (Latitude__c, Longitude__c) for data preservation, but Twenty's interface does not render them as a map pin.

FieldPro allows a Contact to associate with multiple Outlets. In Twenty, People has a single primary CompanyId. Secondary associations are preserved as a custom text or multi-select field listing the additional outlet names, or as Notes attached to the People record.

When FieldPro models outlet hierarchies with parent outlets containing child outlets, these relationships map to Twenty's Company parentId field. The parent Company must be migrated first so its Twenty ID is available; child outlet rows in the import CSV then reference the parent's identifier in the parentCompanyId field to establish the hierarchy in Twenty's data model.