Migrate from Handyman to Pipedrive

Handyman contacts migrate as Pipedrive People. Pipedrive Person stores name, email, phone, and custom fields. All standard contact properties map directly. A Pipedrive Person can link to one Organization (company) via the org_id field — we resolve this from the Handyman company association.

Handyman company records map directly to Pipedrive Organizations. Organization stores business name, address, domain, and custom fields. Multi-contact companies in Handyman collapse to a single Organization record; each linked Person receives the same org_id reference in Pipedrive to maintain the relationship. If Handyman stores multiple addresses per company, the primary address is used and secondary addresses stored in a custom field.

Handyman job or project records migrate as Pipedrive Deals. The job name becomes the Deal title, job amount or estimate maps to Deal value, and the current status (e.g., Scheduled, In Progress) maps to a Pipedrive Stage within your chosen Pipeline. One Deal is created per job record.

Handyman status values (e.g., New, Assigned, In Progress, Completed, Invoiced) become Pipedrive Stage names within a Pipeline. We create one Pipeline in Pipedrive that mirrors your Handyman workflow, with each status value mapped to a named stage in sequence order. Stage probability is assigned per stage for forecasting continuity.

Handyman call logs migrate as Pipedrive Activities with type=calls. Each activity records the subject, duration, outcome (if stored), timestamp, and owner. Activity is linked to the associated Person and, if applicable, the related Deal via the deal_id reference field in Pipedrive.

Handyman email records migrate as Pipedrive Activities with type=emails. Subject, body content, direction (sent/received), timestamp, and owner are preserved. Email content maps to the body field; direction is stored in a custom field if needed for reporting. Note that Pipedrive requires email sync integration to view full email threads natively.

Handyman meeting or site visit records migrate as Pipedrive Activities with type=meetings. Start time, end time, location, and subject are preserved. If your Handyman records include attendee lists, we link the meeting activity to the relevant Person records in Pipedrive.

Handyman notes migrate as Pipedrive Notes attached to Person, Organization, or Deal records. Pipedrive notes support plain text and basic formatting. If notes contain embedded images or file references, we download and re-attach them as Pipedrive file objects linked to the parent record.

Handyman custom fields on contacts (e.g., service tier, technician assigned, preferred contact method) migrate to Pipedrive custom fields scoped to the Person object. Pipedrive requires pre-creation of custom fields before data import — we deliver a custom field creation guide with field name, type, and pick-list options so your Pipedrive admin creates them before migration day.

Handyman custom fields on job records (e.g., service type, property address, work order number, parts used) migrate to Pipedrive custom fields scoped to the Deal object. These carry through as reference data in Pipedrive's pipeline view and are available for automation triggers once re-built in Pipedrive.

Handyman user or technician records resolve to Pipedrive Users by email match. All records owned by a matched user inherit the correct OwnerId in Pipedrive. Users without an email match or who do not exist in Pipedrive are flagged before migration — your team either creates the Pipedrive user first or assigns records to a fallback owner during the migration run.

Handyman file attachments (e.g., job photos, work orders, signed documents) are downloaded and re-uploaded to Pipedrive as Files linked to the parent Person, Organization, or Deal record. Pipedrive's file storage has plan-based limits (5GB per user on Essential, scaling up). We flag files exceeding Pipedrive's per-file size limits before import.