Migrate from APRO CRM to Salesforce Sales Cloud

APRO CRM contacts map 1:1 to Salesforce Contacts. Each contact must resolve to an AccountId — contacts without a primary APRO company association land on a default 'Unassigned Account' record, or your admin can specify a default Account to populate before migration runs.

APRO contacts who are active buyers or tenants but not yet under contract route to Salesforce Lead. Your team specifies the APRO contact status values that should split to Lead vs. Contact. Unconverted APRO contacts with a pipeline deal become Opportunities with a Contact Role rather than a Lead.

APRO CRM company records (which include brokerages, property-management firms, and landlord entities) map to Salesforce Accounts. APRO owner records — individual agents or brokers — map to Salesforce User records for owner resolution, not Accounts. Multi-level APRO company hierarchies (parent/branch) map to Salesforce ParentId on Account.

APRO CRM listings have no native Salesforce equivalent. We create a Property__c custom object with fields for address, listing status, price, property type, and listing agent. The listing's primary contact links via ContactId lookup. Your admin pre-creates the object per FlitStack's schema plan, or we provision it via the Metadata API.

APRO CRM deals (offers, closings, lease agreements) map to Salesforce Opportunities. The deal's associated listing becomes Property__c lookup on the Opportunity. APRO deal stage names map to Salesforce StageName values — each APRO pipeline generates a Salesforce Sales Process keyed by RecordTypeId.

APRO CRM pipelines (residential, commercial, rental) become Salesforce Sales Processes tied to Record Types. Each APRO pipeline requires a Salesforce RecordType on Opportunity so stage pick-list values are correctly scoped. Your admin creates record types in Setup before the migration validates field mapping.

Stage values are mapped value-by-value per Salesforce record type. Stage probability, forecast category, and stage-entry timestamps are preserved as custom fields (Stage_Entered_Date__c) on the Opportunity. APRO stage-entered dates migrate as Stage_History__c JSON or individual datetime fields per your reporting preference.

APRO CRM call logs (duration, disposition, call direction, agent ID) migrate as Salesforce Tasks with Type='Call'. Original call start time maps to ActivityDate or Task.WhatId for association to the Contact or Opportunity. Call disposition maps to a custom Call_Disposition__c field on Task since Salesforce standard Task has no disposition field.

APRO CRM email logs migrate as Salesforce Tasks with Type='Email'. Subject, body preview, and timestamp are mapped to Task.Subject, Description, and ActivityDate respectively. Full email body is stored in Task.Description. Thread ID is preserved in Email_Message_ID__c for reference. Attachments associated with the email are downloaded and re-uploaded as Salesforce Files linked to the Task record.

APRO property showings and meetings migrate as Salesforce Events with original start/end times, location, and who ID preserved. The showing's related listing (Property__c) is linked via WhatId on the Event. Attendees map to EventWhoIds referencing the relevant Contact records. Reminders and recurrence patterns from APRO are also transferred to ensure calendar consistency in Salesforce.

APRO CRM notes and listing comments migrate as Salesforce Notes (the enhanced Notes object, not the legacy Note). Rich-text formatting is preserved where APRO exports it as HTML. ParentId links to the associated Contact, Opportunity, or Property__c record. Any file attachments included with the notes are migrated as Salesforce Files and linked to the parent record.

APRO document templates (listing presentations, offer letters, closing documents) are a platform-specific feature with no Salesforce native equivalent. We export template definitions as JSON — field placeholders, conditional logic, and formatting rules — so your admin can rebuild them in Conga Composer, Salesforce Documents, or DocuSign CLM.

APRO CRM's automatching algorithm — which alerts buyers when listings match their criteria — has no Salesforce equivalent. This automation must be rebuilt using Salesforce Flow with criteria-based email alerts or Salesforce Data Cloud actions. We export the automatch rules as a specification document.

APRO CRM attachments (listing photos, contracts, disclosures) are downloaded and re-uploaded as Salesforce Files attached to the relevant Property__c, Contact, or Opportunity record. File size limits apply — Salesforce Files default to 25MB per file. Original file names and content versions are preserved during the transfer to maintain document integrity and audit trails.