Migrate from Onsite CRM to Pipedrive

Onsite CRM contact records with name, email, phone, and company association map directly to Pipedrive Person records. We use the contact's email address as the deduplication key during import. Company association maps via the Onsite CRM company field to the corresponding Pipedrive Organization lookup, which we resolve before inserting Person records to satisfy the relationship.

Onsite CRM company or account records map to Pipedrive Organization. We extract company records first in the migration sequence so that the Organization exists before any Person record that references it is imported. Company address, domain, and industry fields map to the corresponding Organization fields, with any unmapped fields flagged for manual enrichment post-migration.

Onsite CRM deal records map to Pipedrive Deal with deal value, close date, and stage name transferred. We pre-create the Pipedrive pipeline stages to match the Onsite CRM stage names and probability percentages before inserting any Deal records. Any deal without a matching stage in Pipedrive is placed in a default stage pending customer confirmation.

Onsite CRM pipeline stages are customer-specific configurations that vary in count and naming. We extract the full stage definition from the Onsite CRM UI during scoping, create the corresponding Pipedrive pipeline with matching stage order and probability percentages, and disable the default Pipedrive pipeline so that all deals map to the migrated pipeline.

Onsite CRM call logs, SMS threads, and email records map to Pipedrive Activity records with type (call, email, note), timestamp, and content preserved. We note that the Weebly-hosted UI may not expose all activity history in a single downloadable export; we flag any activity types that require separate extraction requests during scoping. Activities are imported after Person and Organization records so that the activity-owner relationship resolves correctly.

Onsite CRM task records with due date, assignee, and completion status map to Pipedrive Activity records with type set to task. Assignee resolution uses email matching against the Pipedrive user table. Any task with an assignee email not yet provisioned in Pipedrive is placed in a reconciliation queue for the customer admin to resolve before migration resumes.

Onsite CRM user records map to owner fields on Person, Organization, and Deal records in Pipedrive. We match by email address. Any Onsite CRM user without a matching Pipedrive user is flagged in the scoping report and must be provisioned before record migration begins, since Pipedrive requires a valid OwnerId on all core objects.

Custom fields on any Onsite CRM object require manual mapping during scoping. We request a screenshot walkthrough of the Onsite CRM custom field configuration and pre-create the corresponding custom fields in Pipedrive with matched data types before any records load. Text fields, number fields, date fields, and picklist fields each map to Pipedrive's equivalent custom field type. Dropdown options are created in Pipedrive to match the source values exactly.

Tags applied to Onsite CRM contacts or deals migrate as Pipedrive Labels. We extract the full tag taxonomy during scoping, create matching Labels in Pipedrive, and apply them to the corresponding Person or Deal records during import. Tags used inconsistently in the source (free-text applied without a controlled vocabulary) are flagged for normalization during the data-cleanup phase.

Onsite CRM does not appear to expose a structured document management or file attachment object through its UI export. Any file attachments referenced in activity records or deal notes require a separate file extraction step from the Weebly-hosted environment, which may involve customer-assisted download from the Onsite CRM interface. We flag this as a manual step in the scoping report and do not include file migration in the standard migration scope.