Migrate from Jobnimbus to Salesforce Sales Cloud

JobNimbus Contact maps 1:1 to Salesforce Contact. The primary company link in JobNimbus creates Contact.AccountId in Salesforce, so the Account must be migrated first to resolve the lookup. If the Contact has multiple addresses, they are collapsed into a single billing‑shipping address pair in Salesforce, preserving the primary address as the mailing address and the secondary as the shipping address. Contact roles are retained as OpportunityContactRole records linked to the migrated Contact.

JobNimbus Company maps to Salesforce Account. Parent-company hierarchies in JobNimbus map to Account.ParentId. Multi-location counts in JobNimbus (up to 2 on Pro, 5 on Premium) do not have a direct Salesforce equivalent — stored as a custom integer field or mapped to Account Number.

JobNimbus Job is the core work entity and maps to Salesforce Opportunity, the closest analogue for tracking a revenue-generating project. Job status (from the Board) maps to Opportunity.StageName via value mapping per Board. The Job's primary contact becomes the Opportunity's primary Contact (via OpportunityContactRole). If Jobs represent fixed-scope projects rather than sales deals, a custom Job__c object may be appropriate — flagged in the migration plan.

Each JobNimbus Board corresponds to a Salesforce Sales Process keyed by RecordTypeId. Teams with multiple Boards in JobNimbus end up with multiple Record Types in Salesforce — each requiring its own page layout, field-level security, and stage pick-list values. We deliver the record-type setup plan before data lands.

JobNimbus Board column names (e.g., Prospect, Scheduled, In Progress, Complete) map value-by-value to Salesforce Opportunity Stage values. Each stage can carry a probability percentage and forecast category. Stage-change timestamps from JobNimbus are preserved as custom datetime fields for historical reporting.

JobNimbus Estimates with line items map to Salesforce Quotes linked to the Opportunity, or directly to OpportunityLineItems if the team uses Salesforce price books. Estimate totals, tax, and discount fields map to corresponding Quote or Opportunity fields. QuickBooks-linked line items may carry QB-specific IDs preserved as custom fields.

JobNimbus Invoices and Payments map to Salesforce Order records with custom fields for payment status, amount paid, and QuickBooks sync ID. Full accounting ledger detail does not migrate — financial reconciliation remains in QuickBooks. We surface the QBInvoiceID__c and QBPaymentID__c for reference linking.

JobNimbus custom field types map directly: Date → Date, Decimal → Number (18,2), Number → Number (18,0), Text → Text (255). The Salesforce admin must create these __c fields in the target org before migration — we provide the field creation manifest with API names and types.

JobNimbus Engage SMS threads map to Salesforce Tasks with Type = 'SMS'. Original timestamps, message content, and contact links are preserved. SMS history is stored as a long-text custom field on the Task or via an AppExchange SMS app re-link.

JobNimbus Automations do not migrate — they reference JobNimbus-specific objects, triggers, and QuickBooks conditions that have no Salesforce Flow equivalent. We export the automation definitions (trigger object, conditions, actions) as a structured JSON document your Salesforce admin uses as a rebuild blueprint for Flow.

JobNimbus file attachments on Contacts, Companies, and Jobs re-upload to Salesforce Files (ContentDocument/ContentVersion model). Files linked to Jobs that become Opportunities retain the OpportunityId relationship. File size limits: Salesforce default 25MB per file; larger files chunked or linked via URL reference.

JobNimbus user records are matched to Salesforce Users by email address. Unmatched users are flagged before migration — the team either creates Salesforce users or assigns records to a fallback user. JobNimbus role-based access (Admin, Sales, Field) maps to Salesforce Profile and Permission Sets.