Migrate from Delivra to Zoho CRM

Delivra Contacts with lifecycle stage of Subscriber or Lead map to Zoho CRM Lead. Lifecycle stage of MQL, SQL, Customer, or Evangelist map to Zoho CRM Contact attached to an Account. We apply the split rule using Delivra's lifecyclestage property at migration time and preserve the original stage value in a custom field delivra_lifecycle_stage__c on both Lead and Contact for reporting continuity.

Delivra Company records map directly to Zoho CRM Account. The domain field becomes the Account Website. Account is created before any Contact import to satisfy the Account-Contact lookup. Companies without associated Contacts are imported as standalone Accounts.

Delivra Custom Tables with a 1:1 relationship to Contact (one additional profile table per contact) map to a Zoho CRM Custom Module with a lookup field linking to the Contact record. We create the custom module schema in Zoho first, define the lookup field, and resolve the Contact External_ID during import.

Delivra Custom Tables with 1:many relationships (one contact has many related records, e.g., properties, vehicles, subscriptions) are mapped to a Zoho CRM Custom Module with the Contact External_ID stored as a denormalized field on every row. Zoho's 300-field limit applies per module; tables exceeding this require splitting across two modules.

Delivra Custom Tables with many:many relationships use junction objects in Delivra to resolve Contact-to-Related-Record associations. We map these to a Zoho CRM Custom Module with a Contact lookup plus a second lookup field pointing to the related record module, or denormalize both foreign keys into a single module row if the junction cardinality is tractable.

Delivra segments defined as static contact lists map to Zoho CRM Tags on the Contact record. Dynamic segments built from filter conditions require manual rebuild as Zoho saved filters using equivalent field-based criteria. We document every segment definition including its filter conditions as a Zoho filter specification for the customer's admin to implement.

Delivra Campaign records (name, status, targeting criteria, associated content) map to Zoho CRM Campaign with Campaign Type, Status, and Start Date preserved. Email content within campaigns migrates as HTML blocks or attachments for manual re-insertion in Zoho Campaigns or the customer's chosen email delivery tool.

Delivra visual workflow logic including triggers, decision branches, time delays, and action sequences is extracted and documented in a written inventory with every step described in Zoho Blueprint format. Workflows are not migrated as functional objects. The customer's admin rebuilds them in Zoho Blueprint using the inventory as a step-by-step guide.

Delivra lead scoring models with point values assigned to contact attributes and behaviors are exported as a scoring rules document. We migrate the most recent numeric score per contact as a custom field delivra_lead_score__c on the Lead or Contact. The scoring model must be re-implemented in Zoho using custom fields and workflow rules or Blueprint logic.

Delivra email templates built with the drag-and-drop editor are exported as HTML or reconstructed from content blocks. Complex templates with conditional content, dynamic personalization tokens, or interactive elements require manual rebuild in Zoho Campaigns or the destination email editor. We deliver a content inventory with HTML asset files and token mapping.