Migrate from Textline to Pipedrive

Textline Contacts migrate to Pipedrive Person records using the phone number as the primary dedupe key (phone, mobile, and other phone fields checked in order). Email, name, tags, notes, and any custom address book fields (Standard/Pro plans only) map directly. If the customer uses a Standard or Pro plan, we map all custom address book field names and values to Pipedrive custom Person fields. Essentials-plan accounts do not have custom fields in Textline, so we fall back to standard contact fields only. The original Textline contact creation date migrates as a custom field for audit.

Textline's Department structure groups phone lines by location or function. We map each Department to a Pipedrive Organization record, using the department name as the Organization name. The phone number associated with each department maps to the Organization's phone field. If a Textline contact is assigned to a department, we link the Person to the corresponding Organization via Person.organization_id. Note that Pipedrive does not have a native multi-number routing equivalent; department-based assignment logic documented during discovery must be rebuilt as Pipedrive workflow rules or manual assignment.

Textline conversation history splits across two Pipedrive objects: the message content (direction, body, timestamp) migrates as Note records attached to the Person, and the conversation metadata (message count, duration estimate, status) migrates as a Task activity record on the Person. Each conversation produces one Note and one Task, with the Note body containing the full message thread and the Task capturing summary metrics. Conversation export requires per-conversation API calls with pagination for long threads, so large histories (over 50,000 conversations) extend timeline and cost.

Textline Agents migrate to Pipedrive Users, matched by email address. Department assignments from Textline map to Pipedrive role labels or a custom user field (department__c) since Pipedrive does not have a native department grouping structure. Permissions and Custom Roles in Textline have no direct Pipedrive equivalent; we document the permission hierarchy so the customer's admin can map to Pipedrive Role-based access control post-migration.

Tags applied to Textline Contacts migrate to Pipedrive Labels (added in the Pipedrive Android and iOS apps as a cross-object labeling feature). Tag names and taxonomy are preserved as-is. Pipedrive Labels apply across Persons, Organizations, Deals, and Products, providing broader classification than Textline's contact-only tags.

Textline Message Templates (canned replies) are exported with their shortcut codes and body text. We map them to Pipedrive Email Templates if the customer's workflow uses email follow-up from Pipedrive, or to Note records attached to the relevant Person if the template is intended for future SMS use. Because Pipedrive does not have native SMS send, any template intended for text messaging must be recreated in the customer's chosen SMS tool (Twilio, Salesmsg, or native Pipedrive SMS integration).

Textline Announcements (bulk outbound messages) are exported as campaign context records: the announcement body, contact list, and send timestamp are preserved in a Note attached to a placeholder Campaign record in Pipedrive. The sending mechanism must be recreated in Pipedrive's Campaign feature or in the customer's chosen SMS platform post-migration.

MMS attachments within Textline conversations are referenced by URL in the exported message records. We preserve attachment URLs as part of the Note body during conversation migration. Pipedrive does not host file attachments natively via API, so we do not re-download and re-host files. Customers must confirm whether their chosen SMS platform post-migration handles MMS attachment storage independently.

Custom fields on Textline Contacts (available on Standard and Pro plans) migrate to Pipedrive Person custom fields. Field types are mapped: Textline text fields become Pipedrive varchar fields; dropdown fields become Pipedrive set fields with the same options; date fields become Pipedrive date fields. Essentials-plan accounts do not have custom fields in Textline, so this mapping step is skipped for those accounts. We confirm the source plan tier during scoping before designing the destination schema.

Textline Automations trigger on keywords, time, or contact actions. These cannot be migrated programmatically because Textline Automations are not exposed via a public API. We extract the automation name, trigger type, conditions, and actions from the Textline UI during discovery and deliver a written automation inventory with recommended Pipedrive Smart CRM Rule equivalents. The customer's admin rebuilds each automation in Pipedrive's workflow builder post-migration.