Migrate from Jobsite Mobile to Twenty CRM

Jobsite Mobile contacts map directly to Twenty People records. Every People record requires an email to be valid for relation linking during import. Contacts without email are flagged and imported with a placeholder so the full record is not lost.

Jobsite Mobile company records map to Twenty Companies. Company records must be imported before People because Twenty's People import links to a companyId. Parent-company relationships in Jobsite map to Twenty's companyId self-referential relation. This import sequencing ensures that when People records are loaded, they can immediately resolve their companyId lookups without requiring a second pass to backfill missing relations.

Jobsite jobs and work orders are field-service records with no direct Twenty CRM equivalent. We create a WorkOrder custom object in Twenty (Organization tier required) and map job name, status, scheduled date, and assigned contact. If the job carries a revenue figure, it can route to Opportunity instead.

Jobsite Mobile job sites with addresses and location details attach to the parent company or become a standalone Site custom object. Site records link to the parent company via a relation field. Address components split into Twenty's standard address fields on the Company or custom Site object.

Equipment and assets tracked in Jobsite Mobile become a custom Asset object in Twenty linked to the parent Company. Asset fields (name, serial number, status, install date) map to custom fields on the Asset object. If the Organization tier is not available, assets store as structured Notes on the Company record.

Jobsite Mobile service tasks, dispatch items, and checklist steps map to Twenty Tasks. Each Task links to the related People or Company record via Twenty's relation fields. Task status (pending, in-progress, complete) maps to Twenty's Status pick-list. Jobsite task priority levels such as high, medium, and low can be stored as custom select fields on the Twenty Task object if needed for filtering and reporting.

Notes in Jobsite Mobile migrate as Twenty Notes. File attachments are downloaded from Jobsite Mobile and re-uploaded to Twenty's file storage, then linked to the target record. Large files over Twenty's storage limits are flagged before the import runs. Image attachments from job-site photos are migrated as standard Twenty file objects attached to the corresponding Site or WorkOrder record, preserving the visual documentation tied to each job.

Jobsite Mobile users are matched to Twenty Workspace Members by email address. Unmatched owners are flagged in the migration report — the team either creates the Twenty user before migration or assigns those records to a fallback Workspace Member. If a Jobsite user account is inactive or archived, the migration logs the status so the Twenty admin can decide whether to provision an active account or leave the record assigned to the fallback member.

Every custom field in Jobsite Mobile must be pre-created in Twenty under Settings → Data Model before the import runs. We deliver a field-creation checklist specifying the field name, type (text, number, date, select, multi-select), and pick-list values so the Twenty admin can provision them ahead of the migration.

Jobsite Mobile workflows, dispatch rules, and notification automations are not exported by the platform. We export the workflow definitions as a structured JSON document that the team can use as a rebuild reference in Twenty's workflow builder on the Organization tier.

Jobsite Mobile integrations with accounting tools, ERP systems, or scheduling software cannot transfer to Twenty CRM. Each integration must be reconnected or rebuilt. We document the connected systems as part of the migration scope so the team knows what to reconfigure post-migration.