Migrate from Anyone Home to Pipedrive

Anyone Home prospects map directly to Pipedrive Persons in a 1:1 relationship — name, email, phone, and address fields migrate without transformation. Owner resolution uses email matching against Pipedrive Users; any owner without a matching Pipedrive account flags for admin assignment before the full migration run commits. This pre-flight check ensures no records land without an assigned owner and prevents orphaned activity attribution after go-live.

Prospects with lease_status values of 'Inquiry' or 'Under Review' route to Pipedrive Lead rather than Person when your Pipedrive instance uses the dual Lead/Person model. This routing preserves early-stage pipeline visibility in Pipedrive's Lead inbox. Prospects with an Active or Approved lease land directly as Person records with an associated Deal, bypassing the Lead stage entirely and ensuring lease records connect immediately to the correct Person.

Anyone Home property records — including property name, address, unit count, and property type — map to Pipedrive Organizations. Property-level custom fields migrate as Pipedrive Organization custom fields with hash-keyed names that require API-level reference. The hash key assignment happens during Pipedrive field creation via POST /organizationFields and must be documented for accurate data placement during migration writes.

Units do not have a native Pipedrive equivalent. Units belonging to the same Property are merged as a custom field array on the Organization record (e.g., Unit_List__c) or as a separate custom object linked by OrganizationId, depending on your Pipedrive plan. The merged approach preserves unit inventory context without requiring a separate Units table.

Anyone Home leases map to Pipedrive Deals — the lease amount, start date, end date, and status map to Deal value, expected close date, and stage name. Each lease links to the prospect (Person) and property (Organization) via Pipedrive's deal-person and deal-organization associations. The Person and Organization must exist before the Deal is created to satisfy foreign-key requirements.

Lease stages (Inquiry, Application, Under Review, Approved, Lease Sent, Active, Renewal) map to Pipedrive Deal stage values within a configurable mapping table. We recommend creating a dedicated Pipedrive pipeline specifically for lease-tracking with stages that directly match your Anyone Home lease lifecycle. This pipeline structure preserves your existing workflow visibility and ensures consistent stage naming across the migration.

Anyone Home tasks migrate as Pipedrive Activities with type='task'. The due date, assigned owner, and completion status transfer from the source record. Open tasks preserve their original due date for accurate scheduling in Pipedrive; completed tasks migrate with the completed timestamp so your historical activity record remains intact and auditable. Owner assignment uses the same email-match resolution as other objects.

Anyone Home notes migrate as Pipedrive Notes attached to the corresponding Person, Organization, or Deal record. Rich-text formatting in Anyone Home notes is preserved where the source format is compatible with Pipedrive's note body field. Plain-text notes transfer directly without formatting loss. This preservation ensures your historical notes remain readable and contextually complete in Pipedrive after migration.

Anyone Home file attachments on prospects, properties, or leases are downloaded and re-uploaded to Pipedrive Files, then attached to the corresponding record. File size limits from the source system apply during re-upload. Large files exceeding 25MB are flagged for manual review before the migration finalizes to ensure all attachments transfer successfully or are handled via alternative methods such as shared cloud storage links.

Anyone Home owner IDs resolve by email match against Pipedrive Users. A user lookup table is generated before migration — any owner without a matching Pipedrive User account is flagged and must be either invited to Pipedrive or reassigned to a fallback user before the migration runs. This pre-migration check prevents orphaned records and ensures activity attribution continuity after go-live.

Anyone Home custom fields on prospects, properties, or leases require Pipedrive custom fields to be created first using the Pipedrive API (POST /personFields, /organizationFields, /dealFields). We generate the field creation manifest and apply it before data migration so custom data lands in the correct hash-keyed fields. Hash keys are then mapped back to original Anyone Home field names for traceability in the field mapping documentation.

Anyone Home call logs, email records, and meeting entries migrate as Pipedrive Activity records with type values of 'call', 'email', or 'meeting' respectively. Original timestamps and activity owners are preserved to maintain historical accuracy in your audit trail. Email body content migrates to the Activity subject and content fields, ensuring complete communication context is available within the migrated records for future reference and follow-up.