When a Lead is converted into a Contact within the CRM, you may question whether the Marketing Cloud has a similar process to keep all data and tracking against that 'person' within the Marketing Cloud. This is usually a concern when it comes to Contact Utilization within Contact Builder.
When a Lead Converts to a Contact, their SalesforceID will change but they're still the same person with the same information, same data, and same tracking so the Marketing Cloud will need to ensure we're still mapping all of that correctly.
ContactAlternateKeyStore (CAKS), is internal architecture and our way of handling Leads converting to Contacts. CAKS provides that extra layer to the Contacts Model be able to handle the Lead Converting to a Contact.
How CAKS works is, when you create a Lead, the ContactAlternateKey for the LeadID = ContactKey and the AlternateKeyValue and ContactKey are equal.
When you then convert the Lead to a Contact, the values change and the ContactID replaces the LeadID and this then update All Contacts (view in Contact Builder) too, to ensure the record transitions smoothly.
If you want to delete the converted Lead from the Marketing Cloud then you can refer to this article: Marketing Cloud Contact Delete on Lead synchronized data extension deletes converted contact
Email Send and IER details are not transferred to the contact when converting lead but the data is not deleted when we convert a lead and can be accessed by creating reports or by using a SOQL query.
Here is an example of a SOQL query that you can use to fetch the data of all Send definitions:
select et4ae5__EmailId__c,et4ae5__EmailName__c,et4ae5__Lead__c from et4ae5__SendDefinition__c
Here is an example of a SOQL query that you can use to fetch the data of all Individual Email Results:
select et4ae5__Email__c,et4ae5__Contact_ID__c,et4ae5__Lead_ID__c from et4ae5__IndividualEmailResult__c
000389954

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.