Migrate from Evatic to Pipedrive

Evatic customers with multiple contacts map to Pipedrive Organizations for the business entity and Persons for each individual contact. The primary contact becomes the primary Person linked to the Organization. Secondary contacts attach as additional Persons under the same Organization.

Evatic sites linked to a customer merge into the Organization record. Address fields map to Pipedrive's address fields on Organization. Multi-site customers with distinct addresses may generate multiple Organization records or use custom fields for site identifiers depending on your reporting needs.

Evatic service contracts become Pipedrive Deals with custom fields for contract value, start date, end date, renewal type, and billing frequency. The Deal name typically uses the contract number or customer name plus contract period. Pipedrive's Deal stages can be repurposed to represent contract lifecycle states.

Each Evatic work order generates Pipedrive Activities — a Task for the work order itself and a Meeting for on-site visits. Work order status, priority, technician, and resolution notes migrate as custom fields on the Activity or as linked Deal fields. Original work order timestamps are preserved as Activity timestamps.

Parts and materials used during a work order have no native Pipedrive equivalent. These migrate as a custom text or multi-select field on the Activity record. High-volume parts data may require a separate Products setup in Pipedrive linked to Activities via custom fields.

Evatic technicians map to Pipedrive Users by email matching. Active technicians must have Pipedrive user accounts created before migration to ensure their identity is preserved in Activity assignments and Deal ownership records. Inactive or archived technicians can be imported as historical assignments stored in custom fields on completed Activities, maintaining the audit trail of who performed specific work without requiring active Pipedrive accounts for every historical staff member.

Evatic equipment records linked to sites or customers require a custom solution in Pipedrive. We map equipment serial numbers, model numbers, installation dates, and maintenance status as custom fields on the Organization record. High-asset-volume accounts may warrant a Pipedrive custom object for asset tracking.

Evatic SLA terms — response time, resolution time, priority levels, breach flags — have no Pipedrive native equivalent. These migrate as custom fields on Deals or Activities, allowing teams to maintain reference to original service commitments and compliance status. SLA breach history migrates as a custom text field for audit reference, preserving the record of any service level violations that occurred under the Evatic system for compliance and reporting purposes.

Invoice numbers, amounts, payment status, and billing history from Evatic contracts migrate as custom fields on the associated Deal. Pipedrive has no invoicing module — billing records serve as reference data, not active financial records. This means payment terms, credit limits, and invoice aging reports require a dedicated accounting tool or custom integration rather than native Pipedrive functionality. We preserve all billing metadata for audit trails and financial reconciliation.

Evatic work order notes and attached files migrate to Pipedrive Activity notes and Files. File size limits apply (Pipedrive default 256MB per file). Inline images in notes are downloaded and rehosted in Pipedrive's file storage to maintain visual context within records. All attachments are linked to the relevant Activity record, preserving the complete documentation history associated with each work order.

Evatic service categories, work order types, and tags map to Pipedrive Tags on the relevant record (Organization, Person, Deal, or Activity). Tags enable filtering and segmentation in Pipedrive after migration. We map Evatic categories to existing Pipedrive tags where available and create new tags as needed to preserve the full taxonomy. This ensures that existing reporting filters and workflow automations built around Evatic categories can be replicated in Pipedrive without manual retagging of historical records.

Evatic custom fields on any object migrate to Pipedrive custom fields on the equivalent object. Evatic custom modules (e.g., custom entities beyond the standard objects) require Pipedrive custom object creation where supported on your Pipedrive plan. Custom field data types (text, number, date, picklist, checkbox) are mapped to Pipedrive's corresponding field types to preserve data integrity. Any Evatic picklist values are migrated as Pipedrive drop-down options, maintaining the full range of valid values for each custom field.