Migrate from EverPro to Salesforce Sales Cloud

EverPro customers are business entities (companies like HVAC firms, plumbing contractors) and map directly to Salesforce Accounts. EverPro's customer name, business type, and service category fields map to Account.Name, Account.Industry, and custom fields. Address data from EverPro's business location fields migrates to Account.BillingAddress. Parent-account hierarchies in EverPro map to Account.ParentId — the parent customer must be migrated first to avoid circular-reference errors.

EverPro stores individual contacts linked to customers — name, email, phone, job role, and communication preferences. These map 1:1 to Salesforce Contacts with AccountId as the required lookup. EverPro contacts without a primary customer assignment get attached to a default 'Unassigned Account' record flagged in the migration report. Owner assignment on the Contact resolves via email match to Salesforce User records; unmatched owners are flagged for manual assignment before the full run.

EverPro's service-call records (ticket ID, category, agent assigned, duration, resolution status, timestamps) have no direct Salesforce equivalent — Salesforce uses Case for support requests. Each EverPro service ticket becomes a Salesforce Case with Origin='EverPro Import', Type mapped from EverPro's service category pick-list, and Status mapped from EverPro's resolution field. EverPro's agent ID resolves to a Salesforce User lookup where possible. Original EverPro ticket number is stored in Case.CaseNumber or a custom EverPro_Ticket_ID__c field.

EverPro's Customer Loyalty module assigns tiers (e.g., Bronze, Silver, Gold) based on spend and engagement frequency. Salesforce has no native loyalty tier field. We create a custom pick-list field Loyalty_Tier__c on the Account object and populate it from EverPro's loyalty program data. The tier-transition history (dates when a customer moved between tiers) is preserved as a JSON blob in a long-text area field Loyalty_Tier_History__c for reporting continuity.

EverPro's loyalty points system tracks current point balance per customer. This maps to a custom Number field Points_Balance__c on Account. Points expiration dates are stored as a separate custom Date field Points_Expiration_Date__c. Points redemption history is stored as a child Salesforce custom object Loyalty_Redemption__c if the volume warrants it, or as a long-text area field if the list is short.

EverPro's Contact Center module logs call summaries, agent notes, and resolution text attached to service tickets. These interaction narratives merge into Salesforce Tasks linked to the Case object, with Subject='Contact Center Note' and Description containing the EverPro interaction text. Call duration from EverPro maps to Task.CallDurationInSeconds. If the interaction resulted in a follow-up action, a Salesforce Task is also created on the Account for the service team to track.

EverPro's Business Intelligence module stores periodic KPI snapshots (service revenue, job completion rate, average response time). These are time-series records that do not fit Salesforce's standard objects. We create a custom object KPI_Snapshot__c with fields for Snapshot_Date__c, Metric_Name__c, Metric_Value__c, and a lookup to the parent Account. The KPI snapshot object is linked to Account via AccountId and can be reported on using Salesforce's standard reporting or Tableau CRM.

EverPro assigns a customer owner or account manager to each business customer record. The owner is identified by email address in EverPro. During migration, we match the EverPro owner email to the corresponding Salesforce User email. Unmatched owners are flagged in a pre-flight report — the customer is assigned to a default owner (configurable) while the admin resolves the mismatch. This prevents records landing without a Salesforce owner, which would break sharing rules and reporting.

EverPro's Customer Loyalty module tracks referral events — which customer referred which new business. Referral data migrates to a custom Salesforce object Referral__c with fields for Referral_Date__c, Referred_By_Account__c (lookup to Account), and Referral_Status__c. This gives Salesforce users the same referral visibility without losing historical referral attribution from EverPro.

EverPro captures per-contact communication preferences (SMS, email, phone) for the Contact Center module. These map to a custom pick-list field Communication_Preference__c on the Salesforce Contact object. Opt-out flags from EverPro's compliance settings migrate as Contact.HasOptedOutOfEmail and a custom SMS_Opt_Out__c Boolean field.