Migrate from Loyalistic to Zoho CRM

Loyalistic Contact records map directly to Zoho CRM Contacts with standard field mapping (Full Name, Email, Phone, Company Name). Custom properties on the Loyalistic Contact object are identified through field-level sampling during scoping and mapped to typed Zoho custom fields before import. Any enrichment data stored in the Loyalistic Customer Profile is attached as custom field values on the Contact record, with a provenance note that enrichment source may be external.

Loyalistic Customer Profiles aggregate contact details with enrichment layer data. We extract the underlying contact fields for standard mapping and attach profile metadata as custom properties on the Zoho Contact record. Where Loyalistic provides a customer lifetime score or health rating, we map it to a custom numeric field in Zoho.

Loyalistic segmentation rules define group membership based on behavioral or demographic criteria. Segment names and member lists migrate as a flat tag model (Zoho Tags applied directly to Contact records) for simple segment lists, or as a custom Segments module with lookup relationships for complex behavioral segments. The segmentation rule logic itself cannot migrate and must be recreated as Zoho Workflow rules or Blueprint processes post-migration.

Loyalistic tags are flat labels applied to contacts for grouping. We export tag names and apply them 1:1 as Zoho Tags on the Contact record. Zoho Tags support both Contacts and other modules, so if the customer uses tags for Deals or Accounts as well, we map those at the respective module level during migration.

Loyalistic survey responses exist as distinct records linked to the originating contact. We migrate response records into a Zoho custom module named SurveyResponses (API name SurveyResponses__c) with fields for survey name, question text, response value, and timestamp. The module links to the Contact via a lookup relationship. Survey question branching logic is documented and handed off for manual reconstruction in Zoho Forms or Zoho Survey.

Loyalistic campaign records (title, status, timing) map to Zoho CRM Campaigns. Campaign Status and Campaign Type map to Zoho's standard picklist values. We configure the Zoho Campaign module and its related Campaign Member status values before migration so that campaign records are ready to receive engagement history.

Loyalistic engagement events (opens, clicks, sends, conversions) are extracted as activity-level records and attached to the Contact in Zoho CRM as Task records with a custom engagement_type__c field (Email Open, Email Click, Form Submit, etc.). Timestamps, referring URL, and user agent data migrate as additional custom fields on the Task. Campaign membership is recorded via Campaign Member records linked to the Zoho Campaign.

Loyalistic custom fields on the Contact object are identified during discovery through field-level sampling. We create equivalent Zoho CRM custom fields with matching data types before migration begins. Field type mapping follows Zoho's supported types: text fields to Single-Line and Multi-Line Text, number fields to Numeric, date fields to Date, checkbox fields to Checkbox, and picklist fields to Picklist. Zoho's limit is 300 fields per module.

Loyalistic report configurations define saved views and filter criteria. We export report metadata (name, filter logic, column selection) as a written inventory document for the customer's admin to recreate in Zoho Reports or Zoho Analytics. Rendered report data (CSV) can be imported as static records in a custom module or attached as Zoho Analytics datasets.

Loyalistic email and workflow templates exist as reusable content assets. We export template content, variable placeholders, and HTML structure as a written document with the full template body. Template recreation in Zoho Email Templates or Zoho Campaigns depends on the target system's template model and is documented for the customer's admin to rebuild.

Loyalistic Owners referenced on Contact, Campaign, and Engagement records are resolved by email match against Zoho CRM Users. Any Loyalistic Owner without a matching Zoho User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Owner mapping is validated before the Contact import phase begins.