Migrate from ELAINE to Freshsales

ELAINE Contacts map directly to Freshsales Contacts. We extract all standard contact properties (name, email, phone, address) and migrate them as typed fields. Custom fields on ELAINE Contacts are documented during discovery and mapped to Freshsales custom fields, which we pre-create in the destination org before import. Email opt-in and opt-out status from ELAINE's subscriber data migrates to Freshsales's HasOptedOutOfEmail and EmailFormat fields. The contact's enrichment data (added via ELAINE's API enrichment integrations) migrates as read-only custom fields; the external enrichment source must be reconnected post-migration.

ELAINE Target Groups are subscriber segmentation units. Freshsales has no native equivalent segmentation object for contacts, so we convert Target Group memberships into Freshsales Tags (applied via the Tags API) or into a custom multi-select picklist field if the customer has a consistent set of groups across their account. Complex nested Target Group hierarchies are flattened to a single level of tag application, and we document the original group tree as a custom field on each Contact so the customer can reconstruct segments in Freshsales Lists or Reports if needed.

Individual email sends from ELAINE (newsletters, transactional sends) are migrated as send-event records attached to the relevant Contacts via Freshsales's native Contacts module. Send metadata (send date, campaign name, open status, click status) is preserved in a set of custom fields on the Contact record (campaign_send_date__c, campaign_name__c, email_open_count__c, email_click_count__c). If the customer has sent a large number of campaigns, we batch these as related records in a custom module on Freshsales Enterprise rather than as fields on each Contact.

ELAINE Mail Sequences with multi-step triggers, delays, and conditional branches cannot be migrated as automation code to Freshsales because the two platforms use incompatible sequence engines. We extract every Mail Sequence step and its configuration (trigger conditions, step order, delay duration, content variations, A/B test splits) and deliver a written inventory that maps each ELAINE sequence to the equivalent Freshsales Workflow trigger and action. The customer's admin rebuilds sequences in Freshsales Workflows or Sales Sequences (Pro tier and above) using this document as the configuration guide.

ELAINE A/B test configurations with subject line variants, content variants, and send-time variants are documented in a configuration inventory delivered alongside migration. Freshsales does not have a native A/B testing feature for email sends at the Contact level, so we preserve the A/B test configuration as written documentation with a recommendation to replicate the test using Freshsales Workflow conditions or to use Freshmarketer for continued A/B testing post-migration if the customer licenses it.

Custom properties on ELAINE Contacts and Target Groups require field-level schema work in Freshsales before data migration. We audit the full custom field schema during discovery, document field types (text, date, choice, calculated), and create matching custom fields in Freshsales using the Admin Settings > Field Management interface. Calculated fields from ELAINE do not have a direct Freshsales equivalent; we document them and recommend rebuilding as Freshsales formula fields or as calculated values during the post-migration review.

Files attached to ELAINE Contacts or Email Campaigns are downloaded from the source platform and re-associated as Freshsales Attachments or Files (depending on the destination Freshsales edition). File names and the linked Contact record are preserved. Attachments on Email Campaigns are linked to the corresponding contact record or custom module entry rather than to a campaign object since Freshsales does not have a native campaign object equivalent to ELAINE's email send records.

ELAINE's GDPR-compliant subscriber enrichment integrations that pull external data via API are not reconnected during migration. We migrate the enrichment data values as read-only custom fields on the Contact record and deliver a reconnection inventory documenting each enrichment endpoint, the data fields it provides, and the recommended Freshsales integration path (Freshworks Marketplace apps, Zapier, or direct API reconnection). The customer re-establishes live enrichment feeds post-migration in their Freshsales instance.