Migrate from Sierra Interactive to Pipedrive

Sierra Lead records map directly to Pipedrive People with a lead status flag. The lead's name, email, phone, source, and tag list all move. Pipedrive's Leads inbox is populated from these records; conversion creates a Person record linked to a Deal.

Sierra Contact records (agent-facing contacts, not inbound leads) map to Pipedrive People. All standard fields (name, email, phone, and address) are migrated directly. If a contact shares an email address with an existing Lead record in Sierra, FlitStack deduplicates by matching email before writing to prevent duplicate Person records in Pipedrive.

Sierra company records — including listing brokerages, property management firms, or any business entity — map to Pipedrive Organizations. Website URL, industry classification, physical address, and employee count fields map where they exist in both systems. Companies without a name are flagged for manual naming before migration.

Sierra deal records — whether labeled as Transaction, Deal, or Contract — map to Pipedrive Deals. Pipedrive's pipeline and stage model replaces Sierra's pipeline structure. We map Sierra stage names to corresponding Pipedrive stage IDs by matching each pipeline to its Pipedrive counterpart.

Sierra pipelines map 1:1 to Pipedrive Pipelines. Each pipeline in Sierra becomes a separate Pipeline in Pipedrive with its own stage sequence. Stage order and names are preserved; stage probabilities are set to Pipedrive defaults unless you specify custom values.

Sierra tasks, calls, and emails map to Pipedrive Activities. Activity type (call, meeting, task, email) is preserved as Pipedrive's activity_type field. Original creation timestamps and the assigned owner are migrated so the full activity history is intact in Pipedrive from day one.

Sierra notes attached to leads, contacts, or deals become Pipedrive Notes linked to the parent Person, Organization, or Deal record. Rich text formatting is preserved where Sierra stores it; plain-text notes migrate without transformation or loss of content.

Sierra lead tags map to Pipedrive Person tags with tag names copied exactly. If a tag name exceeds Pipedrive's 50-character limit, FlitStack truncates it and flags the record for admin review. Tags containing special characters are normalized to alphanumeric format during migration.

Sierra Lead Ponds have no Pipedrive equivalent. We create a custom field (Lead_Pond__c or similar) on the Person record and populate it with the Pond name. Alternatively, if your team uses Pond as a grouping concept, we can map each Pond to a Pipedrive Tag group for segmentation.

Sierra saved listings and property view history are real estate-specific data with no Pipedrive equivalent. We export this data to a CSV for reference and optionally create a custom field on the Person record to hold the most recent saved listing URL. The full saved-search history requires manual setup in Pipedrive or a third-party real estate integration.

Sierra Action Plans — automated email, text, voicemail, and task sequences triggered by lead behavior — do not migrate to Pipedrive. The trigger model differs fundamentally. FlitStack exports your Action Plan definitions as a JSON reference file; your Pipedrive admin uses this to rebuild automations in Pipedrive's Automation tool.

Sierra users (agents, admins, ISAs) are resolved by email match to Pipedrive users. Unmatched users are flagged before migration — your team either creates the Pipedrive user first or assigns those records to a fallback owner. All deal and activity ownership transfers on the matched records.

Sierra custom fields on Lead records create equivalent custom fields on Pipedrive Person objects via the Pipedrive API. Field types are matched: text to varchar, number to int, date to date, picklist to enum. Pipedrive requires pre-creation of custom fields before bulk import.

Sierra custom fields on Deal records create Pipedrive deal custom fields. For example, a 'Property Type' or 'Listing Status' custom field in Sierra becomes a deal custom field in Pipedrive. We create these fields via API before writing deal records.

Sierra lead source tracking maps to a Pipedrive label on the Person record. Common sources (website, Zillow, Realtor.com, referral) are mapped by name. If you use a structured lead-source field in Sierra, we map it to a custom Person field for reporting clarity.