Migrate from Less Paper Co. to Pipedrive

Less Paper Co. work orders are the core entity. Pipedrive has no native work-order object, so each work order becomes a Pipedrive deal. The work order number, type, status, priority, scheduled dates, equipment, parts, and payment data are stored as custom fields on the deal. The deal's name is the work order title or number. Pipedrive requires a deal to have an organization_id, so the linked customer must be migrated first as an Organization.

Less Paper Co. customer records — name, email, phone, address — map directly to Pipedrive Person fields (name, email, phone, address). Each person must link to an Organization record. For customers without a company in Less Paper Co., we create a solo Organization or attach to a default 'Individual Customer' organization in Pipedrive.

Less Paper Co. business accounts or the company field on a customer record map to Pipedrive Organization. The organization's name, website, industry, and address fields map directly. Organization custom fields in Less Paper Co. (e.g., billing terms, account type) become Pipedrive organizationFields custom fields on the organization record.

Less Paper Co. technician and employee records are resolved by email match against Pipedrive users. Those records become the deal owner and activity owner in Pipedrive. Technicians who do not have Pipedrive user accounts are flagged and assigned to a fallback user during migration. The original technician name is preserved in a custom field on the deal for audit traceability.

Less Paper Co. location records (site name, address, Google Maps coordinates, site-specific notes) map to the Organization record's address fields plus custom fields for site name, map URL, and location-specific notes. Multi-location jobs require multiple Organization records or location stored as a custom field on the associated deal.

Less Paper Co. inventory items — part name, SKU, unit price, quantity on hand — map to Pipedrive Products. Parts consumed per work order are linked to the deal as deal products. Stock quantities and bin locations from Less Paper Co. cannot map natively to Pipedrive and are stored as custom fields on the Product record. Real-time stock tracking requires a separate inventory system.

Less Paper Co. work order completions, status changes, dispatch events, and technician notes migrate as Pipedrive Activities — calls, meetings, tasks, and notes — linked to the deal via deal_id. Original timestamps, activity owners, and subject lines are preserved. The activity type is inferred from the Less Paper Co. event type (completion = task, status change = note, dispatch = meeting).

Less Paper Co. payment history — amount collected, payment method, balance due, payment date — does not have a native Pipedrive equivalent. These fields are stored as custom fields on the Pipedrive deal: payment_status, amount_collected, payment_method, and balance_due. Detailed per-payment records beyond the final status require a separate custom object or external financial system.

Less Paper Co. custom fields on work orders — any fields beyond the standard work order attributes — are created as Pipedrive dealFields. Pick-list fields (work order type, status, priority) require value-by-value mapping against Pipedrive's allowed_values for the field. We surface the full value map before migration runs.

Less Paper Co. file attachments on work orders (photos, PDFs, signed forms) are downloaded and re-uploaded to Pipedrive as files attached to the deal. Signature images are stored as deal attachments or in activity notes. Pipedrive's file size limits (default 100MB) apply; large photo sets are zipped before upload.