Migrate from eMarketeer to Salesforce Sales Cloud

eMarketeer Contacts with lifecycle stage values indicating early funnel (subscriber, prospect, lead) map to Salesforce Lead. Contacts with lifecycle stage indicating qualified or customer status map to Salesforce Contact tied to an Account. We compute the split using eMarketeer's lifecycle properties during scoping, preserve the original eMarketeer lifecycle stage in a custom field em_original_lifecycle__c on both Lead and Contact, and use email as the dedupe key for import.

eMarketeer Contacts frequently store company name as a text property rather than a linked company object. We parse the companyname property, use it as the Account name during import, and link the Contact to the Account via AccountId lookup. Any contact without a resolvable company name becomes an Account with the contact's email domain as the name.

eMarketeer Campaign records (email and multi-channel sends) map directly to Salesforce Campaign. We map campaign name, type, status, start and end dates, budgeted cost, and actual cost. Send history, open rate, and click rate migrate as custom fields on the Salesforce Campaign because Salesforce's native campaign influence tracking operates differently from eMarketeer's engagement metrics.

eMarketeer contacts who received a campaign send become Salesforce CampaignMembers with Status set to Responded if the contact has an open or click event on that campaign. Contacts who received but did not engage become Sent status. We resolve the CampaignMember's ContactId or LeadId based on the contact's lifecycle stage split.

eMarketeer segments are defined by real-time criteria rules, not static membership lists. We snapshot the current segment membership during discovery and create Salesforce Campaign audience lists (static) from the snapshot rather than attempting a live-synced segment. Each eMarketeer segment becomes a separate Salesforce Campaign with an audience of static CampaignMember records. Customers who need dynamic segments post-migration configure Salesforce reporting lists or Flow-triggered segmentation in Salesforce Flow.

eMarketeer flows are automation sequences with trigger-action logic (contact enters segment, wait N days, send email, update property). These do not migrate as code because Salesforce Flow uses a different trigger model and action library. We audit every active Flow during discovery, document its trigger type, conditions, actions, and delay logic, and deliver a written inventory with recommended Salesforce Flow equivalents. The customer's admin rebuilds flows in Salesforce Flow Builder post-migration.

eMarketeer event records (registrations, attendance, session data) map to Salesforce Event. We migrate event name, start and end datetime, location, registration count, and attendance status. Attendee contact resolution uses the same Lead-Contact split logic applied to the segment snapshot. Custom event types require field-level mapping against Salesforce Event's extensible data model.

eMarketeer SMS sends tracked against contacts do not have a native Salesforce Sales Cloud equivalent because SMS routing requires a connected app (Salesforce MobileConnect or a third-party SMS gateway from the AppExchange). We migrate SMS content and send metadata into custom fields on the Task object with a custom TaskSubtype value of SMS. The customer configures an SMS gateway post-migration if native SMS logging is required.

eMarketeer email templates export as HTML blobs. We import them as Salesforce EmailTemplate records. Visual template editors with locked components may not reconstruct identically; we flag any unsupported HTML blocks (such as proprietary conditional markup) and provide the raw HTML for manual cleanup in Salesforce's Lightning Email Builder or Classic HTML editor.

eMarketeer custom properties (industry vertical, product line, custom lifecycle flags) map to Salesforce custom fields on Lead and Contact. We derive the full property schema from the eMarketeer export during discovery (there is no public field registry) and create equivalent custom fields before migration. Property types (text, number, date, dropdown) map to Salesforce field types; enumerations require explicit value mapping against Salesforce picklist value sets.

Campaign-level custom properties in eMarketeer (such as campaign cost center, region, or product line) map to custom fields on Salesforce Campaign. We create these fields during schema design and populate them during campaign import.

eMarketeer engagement events (opens, clicks, unsubscribes) per contact per campaign aggregate into Salesforce CampaignMember status and custom fields rather than individual activity records. For unsubscribe events, we set CampaignMember Status to Unsubscribed and populate HasOptedOutOfEmail on the Contact record. Individual engagement events that the customer wants preserved as activity history map to Task records with a custom engagement type field.

eMarketeer user records (flow owners, campaign managers) map to Salesforce User by email match. Owners without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision before record import begins. OwnerId references are required on most standard object imports.