Migrate from Jobsite Mobile to Pipedrive

Jobsite Mobile contacts map directly to Pipedrive People. Pipedrive Person records require a name field; Jobsite Mobile contacts without a full name are stored with available fields and flagged for review before migration commits. Email, phone, and address fields map directly to Pipedrive's standard Person fields.

Jobsite Mobile companies map 1:1 to Pipedrive Organizations. Organization records in Pipedrive support a Name, address fields, and custom fields. Jobsite Mobile company hierarchies (parent/branch relationships) can be preserved using Pipedrive's organization hierarchy feature or stored as custom fields if the relationship is simple.

Jobsite Mobile projects represent the primary work unit in the source system. These translate to Pipedrive Deals where the deal name captures the project title, amount captures the project value, and project-specific metadata (location, type, status) migrates as custom fields on the Deal. Pipeline and stage in Pipedrive should be configured before projects land so stage values resolve correctly.

Jobsite Mobile work orders associate with projects and track specific deliverables. We merge work-order data into the corresponding Pipedrive Deal as custom fields capturing the work-order ID, type, status, and completion date. If work orders have line items, those migrate as Product records linked to the Deal.

Jobsite Mobile's contact-to-company associations map to Pipedrive's Person-Organization relationship. Pipedrive allows multiple organization links per person; we map the primary company as the default link and attach secondary companies as additional organization relationships on the Person record. Contacts without a company association are flagged for manual review before migration commits. The mapping preserves the relationship order and company role where available.

Jobsite Mobile activity logs (calls, site visits, notes, emails) attached to contacts or projects map to Pipedrive Activities. Activity type maps to Pipedrive's activity_type field (call, meeting, task, email). Original timestamps, duration, and owner information transfers so Pipedrive's activity timeline reflects the full interaction history.

Jobsite Mobile custom fields defined on the Contact object map to Pipedrive Person custom fields. Pipedrive's custom fields are referenced by hash keys in the API but appear with user-defined labels in the UI. We map field values preserving the data type (text, number, date, picklist) and create corresponding custom fields in Pipedrive before migration runs.

Jobsite Mobile custom fields defined on the Project object map to Pipedrive Deal custom fields. Project-specific pick-list values require value-by-value mapping if the destination uses Pipedrive's set or enum types. We generate a value-mapping document for review before the full migration commits.

Jobsite Mobile file attachments associated with projects or work orders migrate to Pipedrive Deal files. Pipedrive's file storage limits vary by plan (5GB/user on Essential up to unlimited on Enterprise). We verify destination storage limits before migrating large file volumes and flag any records exceeding plan limits.

Jobsite Mobile users and owners resolve by email match against Pipedrive Users. Unmatched owners are flagged before migration so your team can either invite them to Pipedrive or assign records to a fallback owner. No record lands in Pipedrive without a valid owner reference.

If Jobsite Mobile stores pre-contact leads separately from contacts, those migrate to Pipedrive's Lead Inbox. Pipedrive routes leads to the inbox for manual qualification before they convert to People and Deals. Lead-specific custom fields map to Pipedrive Lead custom fields.