Migrate from Jobnimbus to monday CRM

JobNimbus Contact records become Items in a dedicated Contact board. Standard fields (firstname, lastname, email, phone, address) map to Monday column types. Owner assignment resolves by email match to a Monday People column. Original create dates map to a custom Created_At__c datetime column since Monday's built-in created_at is migration-timestamp only.

JobNimbus Company records map to Items in a separate Company board. Fields like name, domain, industry, annual revenue, and employee count map to Monday column types. Parent-company hierarchies (where a company has a parent) map to a Link-to-Item column pointing to the parent Company Item.

JobNimbus Job records are the primary entity in the source system and map to Items in a Deals board in Monday CRM. Every Job custom field (roof type, material, square footage, insurance claim number, etc.) becomes a Monday column. Job workflow stages map to a Monday Status column with value-by-value mapping to match your existing stage names.

JobNimbus workflow stages such as New, Contacted, Scheduled, In Progress, and Complete map directly to Monday Status column options, preserving each label and its assigned color. Stage‑enter timestamps from JobNimbus are stored as separate Date columns for every transition, enabling historical pipeline reports to reflect the original timing without manual recreation.

JobNimbus custom fields on Contacts and Jobs are type-aware. Date fields become Monday Date columns, Decimal and Number fields become Monday Number columns (with decimal precision preserved), and Text fields become Monday Text columns. Custom field definitions are preserved as a column-naming convention reference for your Monday admin.

JobNimbus allows multiple companies per contact. In Monday CRM, the primary company association maps to a Link-to-Item column pointing from the Contact Item to the Company Item. Secondary company associations are preserved as additional Link columns or as a JSON-encoded text field if the board structure requires it.

Each Job in JobNimbus has a primary contact. This maps to a Link-to-Item column on the Deals board Item pointing to the primary Contact Item. Monday's subitem structure is not used here because the Job itself is the primary Item.

JobNimbus files attached to Contacts and Jobs are re-uploaded into Monday's File column per Item. File size limits on the destination account apply. We re-download from JobNimbus and re-upload to Monday; original file names and download URLs are preserved in the migration audit log.

JobNimbus owner IDs resolve by email match to Monday CRM users. Unmatched owners are flagged pre-migration with a fallback option: invite them to Monday first, or assign records to a designated fallback user. No Item lands without a resolved owner.

JobNimbus automations (trigger-action rules on job and contact events) have no direct Monday CRM equivalent and cannot be migrated as executable rules. We export all automation definitions — trigger type, conditions, and actions — as a structured JSON and PDF reference document that your Monday admin uses to rebuild automations in Monday's automation builder.

JobNimbus Engage (SMS) conversations are tied to JobNimbus's internal texting platform. Monday CRM has no native SMS module; texting requires third-party integrations like Twilio. SMS history is exported as a text reference file, but the conversation thread cannot be replayed inside Monday CRM.

JobNimbus estimates (legacy or modern) contain line items, quantities, pricing, and templates. These are decomposed: the estimate total and key line items migrate as Number and Text columns on the Job Item, and the original estimate PDF is attached via File column. Full line-item detail requires rebuilding in Monday or a quoting integration.

JobNimbus invoices and payment records are financial instruments tied to JobNimbus Payments (QuickBooks sync, card processing). Monday CRM has no native invoicing or payment processing. Financial records should be exported from JobNimbus and maintained in your accounting system; they do not migrate as CRM Items.

JobNimbus allows multiple boards per workflow. Each board in JobNimbus maps to a separate Monday CRM board with its own Status column, groups, and columns. We create a board-per-JobNimbus-board mapping plan before migration so your Monday workspace mirrors the workflow separation you rely on.