Migrate from eZnet CRM to Salesforce Sales Cloud

eZnet CRM Account records map directly to Salesforce Account. The Account Name, Website, Industry, Phone, Billing Address, and any custom fields migrate as-is. We use Account Name as the primary dedupe key during import and resolve any orphaned records before Contact migration begins. If eZnet CRM stores parent-child account hierarchies, we map the parent Account reference to Salesforce's Parent Account lookup field.

eZnet CRM Contact records map to Salesforce Contact with AccountId resolved at migration time via email-domain or name matching against the Account table. Standard fields (FirstName, LastName, Email, Phone, Title, MailingAddress) migrate directly. Custom contact fields from eZnet CRM (available on Standard and above) are recreated in Salesforce as custom fields on Contact before import.

eZnet CRM Lead records with status values of New, Contacted, Qualified, or Unqualified map to Salesforce Lead with LeadSource, Status, and custom lead fields preserved. eZnet CRM does not distinguish a separate lead-to-contact conversion step, so we carry the eZnet lead status as a custom field eznet_lead_status__c for the customer's admin to use in Salesforce lead assignment rules post-migration.

eZnet CRM Opportunity records map to Salesforce Opportunity with StageName, Amount, CloseDate, Description, and OwnerId resolved. We capture eZnet's pipeline stage order and win/loss definitions and configure corresponding Salesforce Stage values and probabilities in a Sales Process before migration. Opportunity Record Type is set to a default sales Record Type unless the customer requests multiple pipelines mapped to multiple Record Types.

eZnet CRM Opportunity pipelines (if multiple are configured on the source) map to Salesforce Opportunity Record Types with corresponding Sales Processes that whitelist stage values per pipeline. Stage probability percentages migrate from eZnet to Salesforce StageProbability. We configure this in a Salesforce Sandbox before production migration to validate that the stage mapping reflects the customer's actual sales motion.

eZnet CRM call Activity records map to Salesforce Task with TaskSubtype=Call. Call disposition, duration (CallDurationInSeconds), and any notes migrate to custom fields on Task. WhoId on the Task resolves to the migrated Contact or Lead; ActivityDate preserves the original timestamp for timeline ordering.

eZnet CRM email Activity records map to Salesforce EmailMessage (the message content and headers) linked to a Task (the activity timeline entry). The email body, subject, from/to addresses, and timestamp migrate. WhoId on the Task resolves to the migrated Contact or Lead. Email is available as a Professional-tier feature in eZnet CRM, so we confirm email data volume during discovery before sizing this phase.

eZnet CRM task Activity records map to Salesforce Task with Status, Priority, Subject, and ActivityDate preserved. eZnet CRM event Activity records map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Both map to the migrated Contact, Account, or Opportunity via WhatId and WhoId lookup resolution at migration time.

eZnet CRM Document Library metadata (file name, description, created date, owner) migrates as Salesforce ContentVersion records linked to the parent Account or Contact via ContentDocumentLink. The actual file blobs require separate handling: we export the files from eZnet, upload them to Salesforce Files, and link them to the related records. This phase is flagged during scoping because file blob extraction from eZnet may require manual steps depending on available export mechanisms.

eZnet CRM custom fields (available on Standard tier and above) are captured with their data type, picklist values, visibility settings, and related-to object during schema review. We pre-create Salesforce custom fields of equivalent type before any data import. Multi-select picklists, date fields, currency fields, and formula fields each require Salesforce-specific field type selection. The customer reviews and approves the field mapping document before schema deployment.

eZnet CRM Marketing Campaign records with associated campaign members migrate to Salesforce Campaign. Campaign Name, Type, Status, StartDate, and BudgetedCost map to Campaign fields. Campaign members with their Contact or Lead associations migrate to CampaignMember records with Status values (Sent, Responded, Clicked) mapped from eZnet's campaign member statuses.

eZnet CRM Inventory Items (Professional tier and above) map to Salesforce Product2 records with Standard Price Book entries created during import. Item name, SKU, description, and pricing fields migrate. Customers using Salesforce CPQ may require additional Pricebook2 configuration beyond the Standard Pricebook.

eZnet CRM User records with role-based assignments and security profiles are exported and mapped to Salesforce User records by email match. Owner references on Opportunities, Activities, and Contacts resolve to the Salesforce User Id. Any eZnet User without a matching Salesforce User is held in a reconciliation queue; the customer's Salesforce admin provisions missing Users before record import resumes.

eZnet CRM Custom Modules (Enterprise tier) represent non-standard record types that may have no direct Salesforce equivalent. We capture the full module schema including module fields, related lists, and relationships to standard records. Each module becomes a Salesforce custom object with __c API name matching the module label, custom fields recreated in Salesforce, and lookup relationships to Account, Contact, or Opportunity configured before data import.