Migrate from Jobnimbus to Pipedrive

JobNimbus Contact maps 1:1 to Pipedrive Person. All standard contact fields (name, email, phone, address, job title) migrate as Pipedrive Person fields. Custom contact fields in JobNimbus require corresponding Pipedrive custom fields on the Person object. Multi-contact households or sub-contacts collapse to one primary Person record; secondary contacts stored as custom fields for reference.

JobNimbus Job maps to Pipedrive Deal. The job name or job number becomes the Deal name. The job estimated amount maps to Pipedrive's Deal Amount field. Board stage becomes Pipedrive deal stage or a custom stage field depending on board complexity. Jobs with no financial value still migrate as Deals with zero or blank amount — your Pipedrive pipeline handles them the same way as revenue-bearing deals.

JobNimbus Boards are Kanban-style workflow stages for jobs. Each JobNimbus Board becomes a Pipedrive Pipeline. The board's stages (e.g., Lead, Proposal, Sold, Job Complete) map to Pipedrive Pipeline stages. Stage probability values in Pipedrive are set per stage — we map JobNimbus stage order and apply default probabilities, which your team can adjust in Pipedrive settings.

JobNimbus stage names within a board map to Pipedrive stage names per pipeline. Each stage name is matched by string value — e.g., 'Sold' in JobNimbus maps to 'Won' or a custom stage name in Pipedrive. If JobNimbus uses numeric stage IDs, we use the stage label for the value map. Stage-enter timestamps preserved as custom datetime fields on the Deal in Pipedrive.

JobNimbus Estimates are financial documents linked to jobs with line items, quantities, and pricing. Pipedrive has no native estimate object. We migrate estimate total and line-item summary as custom fields on the Pipedrive Deal (Estimate_Amount__c, Estimate_Notes__c). Full line items are preserved as a formatted note or attachment. Rebuilding estimates in Pipedrive requires using Pipedrive Products or a third-party quoting tool post-migration.

JobNimbus Invoices track billing status, amounts paid, and QuickBooks sync status. Pipedrive has no native invoice object. Invoice total, balance due, and payment status migrate as custom fields on the Pipedrive Deal. QuickBooks integration must be re-established in Pipedrive — the existing JobNimbus invoice records become historical reference data in Pipedrive deal notes.

JobNimbus custom fields on Contacts (Date, Decimal, Number, Text types) map to Pipedrive Person custom fields. Pipedrive supports 16 custom field types — we match the closest Pipedrive type for each JobNimbus field. Date maps to Pipedrive date, Number/Double maps to double, Text maps to varchar. Pipedrive generates a hash-key for each custom field — field keys are unique per Pipedrive account and must be created before data load.

JobNimbus custom fields on Jobs migrate to Pipedrive Deal custom fields using the same type-matching logic as Contact custom fields. Job-specific custom fields capturing job-type data, inspection results, or insurance claim IDs become Pipedrive Deal fields. These are created in Pipedrive before migration runs — the field key hash is noted for the mapping plan.

JobNimbus Suppliers (material vendors, subcontractors) map to Pipedrive Organizations. Supplier name becomes Organization name. Supplier contact info migrates as Organization phone, address, and primary contact fields. Supplier records with no person contact still create an Organization in Pipedrive — person-level records for supplier contacts are optional and handled case-by-case.

JobNimbus logged activities (calls, emails, meetings) on contacts and jobs migrate as Pipedrive Activities linked to the corresponding Person or Deal. Activity type, subject, date, and notes are preserved. Pipedrive Activities support Call, Meeting, Task, and Note types — we map JobNimbus engagement type to the matching Pipedrive activity type. Original timestamps and owner assignments are preserved via Pipedrive API.

JobNimbus file attachments on contacts and jobs (photos, contracts, proposals) are downloaded and re-uploaded to Pipedrive as Files linked to the Person or Deal record. File size limits apply — Pipedrive's default upload limit is 50MB per file. Files larger than this are flagged for splitting or alternative storage (e.g., cloud link stored as a custom field). Inline images in notes are extracted and re-hosted as Pipedrive Files.

JobNimbus financing records (Sunlight Financial and similar integrations) track financing application status and approved amounts per job. Pipedrive has no native financing object. Financing status and approved amount migrate as custom fields on the Pipedrive Deal (Financing_Status__c, Financing_Approved_Amount__c). The Pipedrive App Marketplace offers financing app integrations that must be re-connected post-migration.

JobNimbus automations (trigger-based actions on contacts and jobs) have no Pipedrive equivalent and cannot be migrated. Pipedrive automations and sequences use a different event-action model and must be rebuilt from scratch. We export your JobNimbus automation definitions as a reference document for your Pipedrive admin to use during rebuild.

JobNimbus Engage provides a shared texting inbox linked to contacts. Pipedrive has no native Engage equivalent — texting in Pipedrive requires the Campaigns app or a third-party SMS integration. Engage message history migrates as Activity records with type='note' and a custom field flagging the channel. Post-migration, your team sets up a Pipedrive-compatible SMS tool.