Migrate from Anyone Home to Salesforce Sales Cloud

Anyone Home Prospects with lifecycle status 'New', 'Touring', or 'Applied' route to Salesforce Lead. Prospects marked 'Lease Signed' or 'Active Resident' route to Salesforce Contact and attach to the Account representing the property. Split logic uses the Anyone Home lifecycle_status value at migration time.

Standard contact fields on Anyone Home Prospects map directly to Salesforce Lead fields: first name, last name, email address, phone number, and lead source. Original create date preserved as custom field since Salesforce CreatedDate reflects migration timestamp. If a field is missing in the source, we flag it for manual review to avoid silent data loss.

Anyone Home tracks which properties a prospect toured. In Salesforce, this becomes a custom 'Toured_Properties__c' text field on the Contact, listing property names, plus Activity records (Tasks) logging each showing with date, property, and agent. If multiple tours occurred, we concatenate the property names in the text field and create separate Task records for each event to preserve full history.

Each Anyone Home Property (apartment community or building) becomes a Salesforce Account record. Property name maps to Account.Name, address fields map to BillingAddress, and unit count maps to NumberOfEmployees as a proxy for portfolio size. Parent property relationships (if community has buildings) map via ParentId.

Anyone Home Units (individual apartments) require a custom Unit__c object in Salesforce, related to the Property Account via Lookup. Fields include Unit_Number__c, Bedrooms__c, Bathrooms__c, Square_Footage__c, Market_Rent__c, and Unit_Status__c (Available, Leased, Notice Given). We also recommend adding a 'Lease_End_Date__c' field on Unit__c to track upcoming lease expirations and schedule renewal outreach tasks automatically via Salesforce Flow.

Active leases become Lease__c records linked to the Unit and Contact (resident). Move-in date, move-out date, monthly rent, security deposit, and lease term migrate as custom fields. Open opportunities for upcoming lease renewals map to Salesforce Opportunity with custom Lease_Renewal__c flag.

Anyone Home payment records (rent amounts, due dates, payment status) migrate as custom Payment__c records related to Lease__c. Payment date, amount, and status (On-Time, Late, NSF) preserved for resident performance reporting in Salesforce. We also map the original payment identifier from Anyone Home to a custom field on Payment__c for audit trails and reconciliation against the source system.

Anyone Home Leasing Agents are matched to Salesforce Users by email address. If no matching user exists, agents are flagged before migration — your team creates Salesforce users or assigns records to a fallback owner. Agent properties and prospect assignments become custom fields on the User record.

Anyone Home call logs become Salesforce Tasks with Type='Call' and Subject containing the prospect name. Email logs become Tasks with Type='Email'. Showing appointments become Salesforce Events with StartDateTime, EndDateTime, and WhatId linking to the Property Account. If the prospect name is missing, we use the email address as the Subject to ensure the Task remains traceable.

Lease documents, ID copies, and prospect attachments from Anyone Home re-upload to Salesforce Files, linked to the corresponding Contact or Lease__c record. File size limits (25MB default) apply; oversized files flagged for manual handling. We also preserve the original file name and upload date as metadata on the Salesforce File record, making it straightforward to reference the source document.

Anyone Home custom fields on Property (e.g., Amenities, Year Built, Pet Policy) become custom fields on the Salesforce Account or Unit__c object. Field type conversion applied: pick-lists become pick-lists, dates become dates, numbers preserve precision. If a custom field contains a multi-select list, we map it to a Salesforce multi-select picklist, preserving all selected values.

Anyone Home workflows, automated message sequences, and follow-up triggers do not migrate. They must be rebuilt in Salesforce Flow. FlitStack exports the workflow definitions as a structured JSON reference for your Salesforce admin to use during the Flow build phase.