Migrate from Lemon Tech to Pipedrive

Lemon Tech Contact records map directly to Pipedrive Person. Standard fields (name, email, phone, address) migrate as-is. Any custom contact properties from Lemon Tech map to Pipedrive custom fields on Person, which we pre-create with matching field types before import. Owner (user) resolution is by email match against the Pipedrive User table; unresolved owners are held in a reconciliation queue for your admin to provision.

Lemon Tech's standard Entity records (non-contact, non-matter) map to Pipedrive Organization. The Entity name becomes Organization name, and any standard address or description fields map to their Pipedrive equivalents. Custom Entity fields from Lemon Tech map to Organization custom fields. We normalize any inconsistent naming conventions (camelCase, snake_case, spaces) to a consistent format during transformation and preserve original field names in a metadata comment field for auditability.

Matter is the primary schema gap. Pipedrive has no native matter object, so we map Matters to Pipedrive Deals with a custom picklist field matter_type (e.g., Legal, Consulting, Transactional) populated from the Matter category or practice area in Lemon Tech. Billable amount migrates to Deal value. Linked contacts from the Matter are resolved to Pipedrive Person records by email and attached as Deal participants. Matter status, open/close dates, and any custom Matter fields (e.g., court jurisdiction, case number) migrate as Deal custom fields. If the Matter has a linked Entity that represents the client, we also link the corresponding Organization as the Deal's Organization.

Lemon Tech User records (name, email, role) map to Pipedrive User by email address. Role and permission context from Lemon Tech is preserved as a custom field user_original_role__c in Pipedrive for reference during post-migration user setup. Active Users migrate as active Pipedrive users; inactive Lemon Tech users migrate as inactive Pipedrive users unless your admin specifies otherwise.

Lemon Tech custom entities are inventoried during discovery, and each is mapped to Pipedrive custom fields on the most appropriate standard object (Person, Organization, or Deal). We pre-create the destination custom fields via Pipedrive's custom fields API before data import. For custom entities that represent a one-to-many relationship (e.g., a custom Entity for Related Cases linked to a Matter), we evaluate whether to flatten as a multi-select picklist, a delimited text field, or a set of link records, depending on data volume and your admin's preference.

Lemon Tech time entries and billing records linked to Matters export via the Entity export function. Billable amount, date, and linked contact reference migrate as Deal custom fields in Pipedrive. Hourly rate and time duration can be stored as numeric custom fields on the Deal. Pipedrive has no native timekeeping or invoicing object, so this data lands as structured custom field values rather than as a separate object. If the customer requires time-tracking workflows post-migration, we document the recommended Pipedrive automation setup during handoff.

File attachments associated with Lemon Tech Entities or Matters export as binary blobs. We handle attachments separately from record data, preserving filenames, MIME types, and parent record associations. Attachments are loaded into Pipedrive as Files linked to the parent record (Deal, Person, or Organization) via the Files API. Very large attachments may require chunked upload handling. If a Matter's attachment is not associated with a specific linked record in Pipedrive after mapping, we attach it to the corresponding Deal.

SQL Wrappers are per-customer configurations that may include custom SQL, joins across multiple Lemon Tech tables, or third-party data. Simple wrappers that export as standard relational tables map to Pipedrive custom fields or Organization/Person custom fields as appropriate. Complex wrappers with multi-table joins, computed columns, or external data sources require manual field mapping; we inventory all SQL Wrapper definitions during discovery and flag any with nested logic as requiring custom mapping work, then deliver a written map of the wrapper output and its recommended Pipedrive destination.

Lemon Tech email records linked to Contacts or Matters map to Pipedrive EmailMessage records (the email content) linked to an ActivityTask record (the activity timeline entry). The Person (WhoId) and Deal (WhatId) references resolve through our parent-record lookup table. Activity timestamps preserve as the ActivityTask date. If Lemon Tech stores emails as plain-text body fields without a structured date, we infer the timestamp from the record's last_modified field.

Lemon Tech call records map to Pipedrive Task with TaskSubtype = Call. Call disposition, duration, and any notes migrate as Task custom fields. ActivityDate is set to the original Lemon Tech call timestamp. Owner assignment resolves by email match against the Pipedrive User table. If the call record references a linked Matter, the Task's WhatId points to the corresponding Deal we created during the Matter mapping phase.

Lemon Tech meeting records map to Pipedrive Activity (Event). Start time, end time, location, and attendee list migrate as Event fields. Attendees resolve to Pipedrive Person records by email and are linked via ActivityPerson records. If the meeting is associated with a Matter in Lemon Tech, we set the WhatId on the Event to the corresponding Deal.

Lemon Tech Note records migrate to Pipedrive Note linked to the parent record (Person, Organization, or Deal) via the notes API. Rich text content preserves as-is. If the Note was linked to a Matter in Lemon Tech, we attach it to the corresponding Deal in Pipedrive. Note author resolves by email to the Pipedrive User; anonymous notes default to the migration service user.