Migrate from Jobnimbus to Microsoft Dynamics 365 Sales

JobNimbus contacts without an attached sold Job route to Dynamics 365 Sales Lead. First name, last name, email, phone, address, job title, and any custom contact fields map directly. JobNimbus owner assignment resolves by email match to a Dynamics user as the Lead OwnerId.

JobNimbus contacts with at least one sold Job route to Dynamics 365 Sales Contact. The primary company on the contact (most recently modified) maps as the AccountId lookup. All standard contact fields carry over; custom contact fields map to custom fields on the Contact table.

JobNimbus company maps 1:1 to Dynamics 365 Sales Account. Company name becomes Account Name; website, phone, address, industry, and employee count map to their Dynamics equivalents. Parent-company hierarchies in JobNimbus map to the Parent Account lookup in Dynamics. Multi-company contacts collapse to one primary AccountId plus Account Contact Relationships.

JobNimbus Jobs do not map to the native Dynamics Opportunity — their contractor-specific fields (insurance carrier, material type, Xactimate code, roof measurements, supplier) have no standard Opportunity equivalent. We create a custom Job__c table in Dynamics Enterprise to preserve the full job schema. JobNimbus Job ID is stored as Source_Job_ID__c for traceability.

Each JobNimbus Board becomes a Dynamics 365 Sales Process with its own set of Opportunity Stages. Board columns (e.g., Prospecting, Proposal, Negotiation) map to stage names with probability percentages and forecast category assignments. Multi-board setups create multiple Sales Processes — the opportunity's ProcessId links the stage set to the record.

Each JobNimbus board column name maps to a corresponding Opportunity Stage value under the relevant Sales Process. Probability and forecast category are applied per Dynamics's stage model. Stage-entry timestamps from JobNimbus board history are preserved as custom datetime fields (Stage_Entered__c) on the custom Job__c table.

JobNimbus Estimates map to Dynamics 365 Sales Quotes. Estimate name becomes Quote Name; line items (materials, labor, tax) map to Quote Products. The linked Job's primary contact and AccountId are carried forward. Estimate totals map to the Quote Amount field. Active/accepted/rejected status is preserved as a custom field.

JobNimbus Invoices map to Dynamics 365 Sales Invoices. Invoice number, date, due date, line items, and total map to their Dynamics equivalents. The Invoice's linked Job and Account are preserved for audit traceability. Payment status is carried as a custom field since Dynamics Invoice status is driven by the Order-to-Cash flow.

JobNimbus Suppliers are vendor records. They can map to Dynamics Account records (if used for both customer and vendor relationships) or to a custom Vendors__c table depending on whether your Dynamics instance uses Accounts for both B2B customer and vendor entities. We surface the mapping decision in the migration plan before the run.

JobNimbus file attachments stored against Jobs and Contacts are downloaded and re-uploaded to the corresponding Dynamics record's SharePoint document location or OneDrive folder. Job files attach to the custom Job__c record; contact files attach to the Contact record. File name, size, and upload date are preserved. Inline images in notes are extracted and re-hosted as SharePoint assets.

JobNimbus automations (automated texts, email triggers, task creation, stage-change actions) do not migrate to Dynamics 365 Sales. FlitStack exports your automation definitions — trigger conditions, action sequences, and filter logic — as a structured JSON reference file. Your Dynamics administrator uses this to rebuild equivalent Power Automate flows or classic Dynamics workflows post-migration.

JobNimbus Engage shared texting inbox history does not map to a native Dynamics activity type. We export the text message log as a structured CSV/JSON data file and attach it to the relevant Contact or Job record in Dynamics. A custom Engage_Text__c activity table can be created in Dynamics Enterprise to house the full thread history if your team wants it queryable within the CRM.

JobNimbus custom fields on Contacts and Jobs (Date, Decimal, Number, Text types) map to Dynamics custom fields on the Contact and Job__c tables respectively. The field type is preserved during mapping. Dynamics Enterprise is required if you have more than 15 custom fields per object on the Sales Professional plan.

JobNimbus original create dates for contacts, companies, and jobs are preserved as custom datetime fields (JN_Original_Create_Date__c, JN_Original_Job_Create_Date__c) on the respective Dynamics records. Dynamics's own CreatedDate field is stamped at migration time and does not carry the original source timestamp. These preserved dates maintain historical continuity for reporting, audit trails, and downstream analytics that rely on accurate record origination timestamps from the source system.

JobNimbus owner assignment on contacts and jobs resolves by email match against Dynamics 365 Sales users. Unmatched owners are flagged before migration — your team either invites them to Dynamics first or assigns their records to a designated fallback user. No record lands without a valid OwnerId.

The JobNimbus internal identifier for contacts, companies, and jobs is stored on each Dynamics record as Source_System_ID__c (or JN_Job_ID__c on the Job__c table). This cross-reference field maintains the permanent link between the original JobNimbus ID and the migrated Dynamics record, enabling delta-run synchronization, supporting rollback operations, and providing end-to-end traceability throughout the migration cycle and beyond.