Migrate from edge CRM to Salesforce Sales Cloud

edge CRM Contact records map directly to Salesforce Contact. We extract all standard fields (name, email, phone, address) plus any user-defined custom fields and map them to typed Salesforce fields. The Contact is inserted after Account to satisfy the AccountId lookup. Email address serves as the dedupe key to prevent duplicate Contact creation during incremental migration windows.

edge CRM Company records map to Salesforce Account. The Company name becomes the Account Name; any website field maps to Account.Website. Account is created first so that Contact imports resolve the AccountId lookup at insert time rather than requiring a post-import relationship fix.

edge CRM stores Contact-Company associations as a relationship graph. We extract every Contact-Company linkage and map it to Salesforce Contact with an AccountId lookup (primary association) or to the Contact's accountId field. For contacts with multiple associated companies, we flag the primary company during scoping and map secondary associations to a custom junction object or Contact account affiliations depending on the customer's data model.

edge CRM Deals map to Salesforce Opportunity. The deal name maps to Opportunity.Name; monetary value maps to Amount; expected close date maps to CloseDate. We resolve the AccountId by looking up the Deal's associated Company against the migrated Account records before Opportunity insert. OwnerId resolves by email match against the Salesforce User table.

edge CRM allows custom stage names and ordering per pipeline. We extract the full stage list (names and sequence positions) from edge CRM during scoping and create a corresponding Salesforce Sales Process with StageName values matching the customer's naming convention. Stage probability percentages migrate as StageProbability on each stage entry in the Sales Process.

edge CRM Lead records (AI-scored prospects distinct from Contacts) map to Salesforce Lead. The edge CRM lead score value migrates to a custom field lead_score__c on the Salesforce Lead object. Lead Status maps to a custom picklist matching the customer's qualification stages. We preserve the Lead's original creation date for reporting continuity.

edge CRM's AI-powered lead qualification assigns a numeric score to each Lead. This score migrates as a custom Number field (lead_score__c) on the Salesforce Lead object. The customer decides during scoping whether to use this score in Salesforce Flow criteria or report on it as a historical data point.

edge CRM call logs map to Salesforce Task with TaskSubtype set to Call. Call duration and disposition migrate to custom Task fields. The ActivityDate is set to the original edge CRM call timestamp to preserve timeline ordering. WhoId links to the resolved Contact or Lead; WhatId links to the related Account or Opportunity.

edge CRM email activity maps to Salesforce EmailMessage (the email body and headers) linked to a Task record (the activity timeline entry). The Task's WhoId points to the resolved Contact or Lead; WhatId points to the related Account or Opportunity. Email thread associations migrate if edge CRM exposes a thread ID or message ID field.

edge CRM meeting records map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Attendee lists map to EventRelation records linking the Event to the corresponding Contact, Lead, or User records. Meeting notes migrate to Event.Description.

edge CRM follow-up tasks map to Salesforce Task with Status, Priority, ActivityDate, and Subject preserved. Completed and open tasks both transfer. Overdue status is stored as a date field rather than a system flag. Owner resolution uses email-to-User lookup.

edge CRM custom properties on Contacts, Companies, Deals, and Leads migrate to Salesforce custom fields on the equivalent object. We extract the full custom field schema during scoping — including field type, picklist values, and default values — and pre-create the Salesforce fields in the destination org before migration begins. Field types map to closest Salesforce equivalents (text to Text, number to Number, date to Date, picklist to Picklist or Multi-Select Picklist).

Documents stored in edge CRM's document management module migrate as Salesforce ContentDocument records linked via ContentDocumentLink to the parent Contact, Account, Opportunity, or Lead. We flag attachments during scoping, assess per-record download availability, and include file attachments in the migration scope only if edge CRM's UI export supports bulk download. Files without a confirmed download mechanism are listed in a separate attachment inventory for manual re-upload.