Migrate from Agent Legend to Pipedrive

Agent Legend contacts map directly to Pipedrive People. The primary fields — name, email, phone, address — carry over as direct field maps. Owner resolution happens by matching the contact's assigned agent email in Agent Legend against Pipedrive user email addresses. Unmatched owners receive a fallback assignment flagged for review before the migration commits.

Agent Legend stores real estate data as contact-level custom properties — a property belongs to a contact rather than existing as an independent entity. FlitStack creates a Pipedrive Organization record for each unique property address encountered in the contact export, populates the Organization with the property custom fields (address, type, status, estimated value) and links the Person back to that Organization via the Person's OrganizationId lookup. This converts Agent Legend's flat contact model into Pipedrive's normalized Person–Organization relationship.

Agent Legend campaigns (circle prospecting, AI campaign builder, two-way texting sequences) have no direct Pipedrive equivalent. Each campaign a contact was enrolled in is recorded as a custom multi-select field on the Person record (Campaign_List__c), preserving the enrollment history. The campaign cadence and messaging content cannot be transferred — those sequences must be rebuilt in Pipedrive Automations or an external tool. FlitStack exports campaign definitions as a reference document for your Pipedrive admin.

Agent Legend's Lily AI assigns a predictive score (0–100) to each contact based on 1,600+ third-party data signals. Pipedrive has no native predictive scoring field. FlitStack creates a custom numeric field (Lily_Score__c) on the Person object, preserving each contact's last-known Lily score as a static value. Pipedrive's optional Lead Scoring add-on (Premium+ plans) can be configured as a live replacement after migration, calibrated against the migrated historical scores.

Agent Legend tracks how each contact entered the system — via portal lead, referral, purchased list, organic, etc. This attribution data lives as a custom property on the contact record. FlitStack maps it to a custom pick-list field on Pipedrive Person (Lead_Source__c), preserving the exact source label from Agent Legend so reporting by original lead source is continuous after go-live.

Agent Legend records each outbound message sent, each reply received, and each call logged as an interaction on the contact record. FlitStack translates these into Pipedrive Activities: type='email' for SMS and email messages, type='call' for voice interactions, and type='task' for follow-up reminders. Original timestamps and the associated agent owner are preserved. This gives Pipedrive a complete engagement timeline on each Person record from day one.

Agent Legend agents (the team members using the platform) are resolved to Pipedrive Users by matching the email address on the Agent Legend agent record to a Pipedrive user with the same email. If an Agent Legend agent has no corresponding Pipedrive user at migration time, their records are assigned to a migration fallback owner and flagged in the pre-flight report. We recommend creating Pipedrive user accounts before migration begins so owner resolution is automatic.

Agent Legend does not have a native Deals or Opportunities object — pipeline tracking is implicit through campaign enrollment and contact status. Pipedrive Deals must be created fresh in Pipedrive after migration. FlitStack can create placeholder Deals linked to each Organization (property) record using the last_modified date as an estimated close date, giving your team a starting pipeline to populate with actual deal values. Alternatively, your team defines deal creation rules post-migration.

Agent Legend does not model deal stages. Pipedrive Pipelines and Stages must be configured by your team before or after migration. FlitStack delivers a Pipeline setup plan based on your Agent Legend campaign count and property transaction types (Listing, Buyer, Lease, etc.), so the pipeline structure is ready when Deals are created.

Agent Legend workflows, circle prospecting sequences, and two-way texting automations are tightly bound to its messaging engine and do not have an exportable definition format. They cannot be migrated. FlitStack exports a human-readable reference document listing every Agent Legend campaign name, trigger condition, and action step so your Pipedrive admin or automation consultant can rebuild the logic in Pipedrive Automations or an external tool.

Agent Legend integrations with third-party tools — lead portal feeds, Zapier connections, Follow Up Boss sync, Lofty CRM sync — are connection-level configurations that do not export. Each integration must be rebuilt in Pipedrive using Pipedrive's native integrations, Zapier, Make, or the relevant third-party's Pipedrive connector. FlitStack documents which integrations were active in Agent Legend so nothing is missed during rebuild.

Agent Legend file attachments (vCards, property documents, contract PDFs stored on a contact record) are downloaded and re-uploaded to the corresponding Pipedrive Person or Organization record. File size limits match Pipedrive's upload constraints per plan. We flag any file exceeding the target plan's limit before the migration runs so you can adjust or archive large files.