Migrate from Access CRM to Salesforce Sales Cloud

Access CRM Contacts with no linked Company or with a lead-status flag route to Salesforce Lead. Contacts with a linked Company and an active pipeline relationship route to Salesforce Contact attached to an Account. We capture the original contact_type or status property during scoping and preserve it in a custom field access_original_type__c on both Lead and Contact for audit and reporting.

Access CRM Company records (sometimes called Account in tenant configs) map directly to Salesforce Account. The company name becomes Account.Name and the primary address maps to BillingAddress. Any circular parent/child references identified during the Access CRM audit are flattened into a single-level hierarchy in Salesforce before import.

Access CRM Opportunities carry Worst/Likely/Best monetary values and a stage-based probability figure. We map Worst to a custom Salesforce field access_worst_value__c, Likely to Amount, and Best to access_best_value__c. The Access CRM stage-based probability migrates as a Salesforce Probability override so that the Opportunity's forecast value reflects the Likely value. If Access CRM probability is not set per record, we derive it from the stage probability configured in the stage-mapping matrix.

Access CRM pipeline stages are tenant-defined free text. We capture every distinct stage name during scoping, produce a stage-mapping matrix, and configure Salesforce StageName picklist values to match. Probability percentages per stage migrate from Access CRM to Salesforce StageProbability. Stages with no mapping default to a 'Archive' stage unless the customer provides explicit direction.

Access CRM Cases (problem-tracking tickets routed to customer-service, warehousing, or accounts teams) map to Salesforce Case. Case status values from Access CRM migrate to Salesforce Case Status picklist; Case priority maps to Case Priority. If the destination Salesforce org includes Service Cloud, we configure a Service Console Record Type. The Case-Contact link resolves via email match after Contact migration completes.

Access CRM User records (name, email, role) are migratable. We map the Access CRM owner assignment on each record to the corresponding Salesforce User by email match. Users without a match go to a reconciliation queue for the customer's admin to provision. Inactive Salesforce Users are supported for historical OwnerId preservation.

Access CRM call logs map to Salesforce Task with TaskSubtype set to Call. Call disposition, duration in seconds, and any external recording URL migrate to Salesforce Task fields. ActivityDate is set from the original Access CRM timestamp to preserve timeline ordering.

Access CRM email history migrates to Salesforce EmailMessage records (body and headers) linked to a Task record on the activity timeline. WhoId points to the converted Lead or Contact; WhatId points to the related Opportunity, Account, or Case. This requires parent-record resolution after Leads, Contacts, and Opportunities are loaded.

Access CRM meeting records map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Attendees resolve to EventRelation records linked to the corresponding Contact, Lead, or User. If Access CRM stores meeting notes, they migrate as Event Description or as a linked Note.

Access CRM standalone notes migrate as Salesforce Note records linked via ContentDocumentLink to the parent Contact, Account, Opportunity, or Case. Note body passes as rich text. Image attachments migrate as ContentDocument records linked to the Note.

Attachments on Access CRM Contacts, Companies, and Opportunities migrate as ContentDocument records. We confirm the destination Salesforce org's file storage limits before migration and flag any attachments that would exceed them. ContentDocumentLink ties each file to its parent record (Account, Contact, Opportunity, or Case).

Access CRM custom fields are tenant-specific and not self-documented. We extract the full field manifest from the Access CRM admin knowledge base during scoping and create matching Salesforce custom fields before any data loads. Field types are mapped: text to Text(255), number to Number, date to Date, picklist to Picklist. Lookup references to other Access CRM objects are stubbed or mapped to Salesforce lookup fields per the cross-module reference resolution plan.

Access CRM web-enquiry forms capture leads directly into the CRM Opportunity or lead flow. Form field structure is tenant-specific. We treat each form as a custom field set and map form fields to Salesforce Lead standard fields or custom fields on Lead. The customer configures Salesforce Web-to-Lead as the replacement form-to-Lead routing mechanism post-migration.