Migrate from Jobnimbus to Twenty CRM

JobNimbus Contact maps 1:1 to Twenty People. The Contact's primary company link resolves to Twenty's companyId relation field. We pull the Contact's first name, last name, email, phone, address, and all custom fields and load them as People records with companyId resolved against previously migrated Companies.

JobNimbus stores contact addresses as structured fields (street, city, state, zip, country). Twenty People has a single addressRaw text field. We concatenate the full address into a single string so it displays in the Twenty record, and optionally split into addressLine1, addressLine2, city, state, country if your Twenty workspace uses the full address object.

JobNimbus Company maps to Twenty Companies. The Company name, domain, industry, phone, and employee count migrate as standard fields. Parent-child company hierarchies in JobNimbus map to Twenty's Parent Company relation if present — companies must be sequenced so parent records load before children to satisfy the foreign-key constraint.

JobNimbus Job is the central project/deal record and maps to Twenty Opportunities. The Job's name becomes Opportunity name, the amount (if priced) becomes amount, the close date maps to CloseDate, and the assigned Contact becomes the Opportunity's personId relation. The Job's Board and Stage determine Opportunity stage mapping — see the stage value-mapping gotcha.

JobNimbus Board stages (e.g., Lead, Proposal Sent, Sold, In Progress, Completed) map to a custom select field on Twenty Opportunities. Each stage name maps value-by-value — if your boards use different stage names per board, we map each board's stage set independently so the correct stage label appears on each Opportunity.

JobNimbus Job-level custom fields (material type, permit number, Xactimate line items) require Twenty custom fields created on the Opportunities object before migration. We create the matching custom field in Twenty (with the correct type: number for numeric values, text for strings, date for date values) and then map each Job's custom field value during the Opportunity load.

JobNimbus Contact-level custom fields (e.g., trade license number, insurance expiry, referral source) become Twenty People custom fields. We audit all custom field names and types in JobNimbus before migration, create the corresponding fields in Twenty (type-matched: Date, Decimal, Number, Text), and migrate values during the People load.

JobNimbus file attachments (photos, contracts, Xactimate estimates) download from the Job record, re-uploaded to the corresponding Twenty Opportunity as a File attachment. File names and original upload timestamps are preserved in the File metadata. Large photo sets from JobNimbus are batched for re-upload to stay within API rate limits.

Contact-level attachments in JobNimbus (e.g., signed contracts, ID documents, certifications) migrate to Twenty People Files using the same download-re-upload process as Job attachments. Each attachment downloads from the Contact record with its original filename, file size, and MIME type preserved. The attachment is re-uploaded to the matching Twenty People record as a File object linked by the migrated People id. A post-migration file audit confirms every expected attachment is present and accessible in Twenty.

JobNimbus notes attached to a Job map to Twenty Notes on the corresponding Opportunity. The note body, author, and original create timestamp migrate. If the note contains rich text, we preserve the formatting as best supported by Twenty's Notes object.

Contact-level notes in JobNimbus migrate to Twenty Notes on the matching People record. The note body text, author name, and original create timestamp are preserved during migration. Notes are sequenced to load after People records so the id reference resolves correctly — this load-order dependency satisfies Twenty's referential integrity requirement that a Note must attach to an existing People record. Rich text formatting is retained where Twenty's Notes object supports it.

JobNimbus Tasks migrate to Twenty Tasks with subject, due date, assigned user, and completion status preserved. Task links to the parent record (Contact or Job) via Twenty's relation field. Open tasks and completed tasks both migrate — completed tasks carry their completion timestamp.