Migrate from solve 360 to Pipedrive

Solve 360 Contacts map directly to Pipedrive People. Standard fields (name, email, phone, address) transfer as typed fields. Custom fields on Contacts export with their field type (text, number, date, selection) and are pre-created in Pipedrive before the People import begins. We use email as the dedupe key to prevent duplicate Person records on re-runs. The Organization lookup on each Person record is resolved after Organization import completes.

Solve 360 Companies map to Pipedrive Organizations. Company name becomes Organization name; domain becomes website field. We import Organizations before People so that the OrganizationId lookup is satisfied at the moment of Person insert. Any Solve 360 Company with no linked Contacts is imported as a standalone Organization. Custom fields on Companies pre-create as Pipedrive custom fields on the Organization object before import.

Solve 360 Tasks map to Pipedrive Activities of type Task. Status, priority, due date, and assignee transfer. Assignee resolution uses email matching against Pipedrive Users, with unresolvable owners held in a reconciliation queue. Task time entries (duration and billing flag) attach as a note on the activity record if the destination Pipedrive plan supports the field, or as a custom note format.

Solve 360 Follow-ups are time-stamped activity records tied to a Contact or Company. They migrate as Pipedrive Activity records with the activity_type set to Note and the body carrying the follow-up content. The original timestamp is preserved as the ActivityDate. We link Follow-ups to the corresponding Person or Organization using the Solve 360 relationship metadata before import.

Solve 360 Support Requests track issue status, descriptions, and conversation history against a Contact or Company. Pipedrive has no native ticket object in standard plans, so we migrate Support Request records as Activity Notes with a custom field capturing the original support status (Open, Pending, Resolved, Closed). Conversation threads append as sequential Note entries on the same Person or Organization. Customers on Pipedrive's Enterprise plan can use Cases if Service Cloud is active, which we configure on request.

Solve 360 Time Records attach to Tasks, Follow-ups, Calls, and Meetings and carry duration, date, billing flag, and parent object reference. We export Time Records grouped by their parent object. During Pipedrive import, each group appends as a structured note on the parent Activity, preserving duration, date, and billing flag. Time Records without a parent are imported as standalone Notes on the associated Person or Organization.

Solve 360 Users are both system actors and assignment targets. We export the full user list and match by email against Pipedrive Users. Any Solve 360 User without a matching Pipedrive User is held in the reconciliation queue for the customer's admin to provision before record import resumes. Active status, name, and email are the only fields that transfer; Solve 360 role permissions do not map to Pipedrive role structures.

Solve 360 custom fields on Contacts and Companies (text, number, date, selection types) export with their definitions and values. We pre-create matching Pipedrive custom fields on the Person and Organization objects before data import, using equivalent field types. Selection fields map to Pipedrive drop-down options; multi-select scenarios map to Pipedrive multi-select fields. We flag any field types that have no direct Pipedrive equivalent (such as Solve 360-specific data types) for manual review during scoping.

Solve 360 pipelines and their stages (names, order, probability) export as a configuration object. We create matching Pipedrive Pipelines and Stages before migration, setting stage probabilities to match Solve 360 values. The customer's Pipedrive admin reviews and approves the pipeline layout in a Sandbox or development account before production import begins. If Solve 360 pipeline assignments are per-record rather than global, we document the per-record assignment logic for manual recreation.

Solve 360 Tags label Contacts, Companies, Tasks, and Support Requests. We export the full tag taxonomy and re-apply them as Pipedrive native Tags, preserving per-record associations. Pipedrive Tags are object-agnostic and apply to People, Organizations, Deals, and Activities, which mirrors Solve 360's tagging model closely.

Attachments on Contacts, Companies, Tasks, and Support Requests are downloaded from Solve 360 with their file metadata (name, type, size, upload date). We re-upload them to Pipedrive and link them to the corresponding Person, Organization, or Activity using Pipedrive's file attachment API. File metadata is preserved in a note attached to the file for audit. Attachments larger than 100 MB are flagged for chunked upload or direct link strategy during scoping.