Migrate from Delivra to Freshsales

Delivra contacts with lifecycle stages indicating early-stage prospects (subscriber, lead) map to Freshsales Lead. Contacts with lifecycle stages indicating sales-qualified or customer status map to Freshsales Contact tied to an Account. The split is computed using Delivra's lifecycle_stage property and stored as a custom text field original_lifecycle_stage__c on the destination record for audit. Email address is the dedupe key for both Lead and Contact migration.

Delivra contact records that represent company-level information (organization name, industry, employee count stored as contact properties) are mapped to Freshsales Account records, with the individual contact mapped to a Contact record linked via AccountId. We extract the primary organization identifier from Delivra contact properties and create the Account before the Contact insert to satisfy the lookup dependency.

Delivra Custom Tables with 1:1 relationships to contacts flatten into Freshsales custom fields on the Contact object. We extract each table's column schema, map data types to Freshsales field types (text, number, date, dropdown, checkbox), and import the values as custom field data. This approach preserves the data without the relational structure, which Freshsales does not support at the Contact level for external table references.

Delivra Custom Tables with 1:many relationships (e.g., contacts linked to multiple subscriptions, properties, or contracts) require a split. We flatten these to a Freshsales custom object with a lookup to Contact, storing the relationship as a denormalized contact_id field. For product-like data (items, SKUs, pricing), we evaluate mapping to Freshsales Product2 records and Pricebook entries if the table structure aligns with a standard product model.

Delivra campaign records include name, status, and targeting criteria. We extract campaign membership data as a custom multi-select picklist on Contact capturing campaign names, or as a Note attached to the Contact record. Freshsales does not have a native campaign marketing object at the CRM tier, so the campaign context is preserved as descriptive metadata rather than a first-class object.

Delivra segment definitions use filter conditions on contact properties. We extract the segment membership for each contact and store it as a custom multi-select picklist on the Freshsales Contact. The segment criteria logic is documented in a written inventory for the customer to re-implement as Freshsales static lists or workflow filters.

Delivra lead scoring values (point-based scores from standard or advanced scoring) migrate as a custom numeric field score__c on Freshsales Contact. The scoring model rules and weight definitions are documented in a written handoff so the customer's admin can re-implement the model using Freshsales Freddy AI scoring on Pro and above or custom workflow rules on Growth.

Delivra click tracking, open tracking, and engagement metrics associated with contacts migrate as Freshsales Task records. Email opens and clicks become tasks of type Email; form submissions become tasks of type form_submission with custom fields for the form name. Activity timestamps are preserved as ActivityDate on the task. Freshsales's native activity timeline displays these records in chronological order against the contact.

Delivra email templates built with the drag-and-drop editor are extracted as HTML and converted to Freshsales email templates. We extract template content, subject line, and personalization tokens. Complex conditional content and dynamic blocks that rely on Delivra-specific syntax are flagged as requiring manual re-creation in Freshsales's template editor. The written template inventory identifies which templates are ready for direct import versus which require rebuild.

Delivra user accounts with role-based permissions migrate by email match to Freshsales User records. Delivra role definitions (Account Admin, Custom Roles, Team Collaboration) are documented in a written permissions matrix that the customer's Freshsales admin uses to assign Freshsales profiles and permission sets. Unlimited user seats on Delivra map to a per-seat Freshsales license count during migration scoping.