Migrate from Altcraft to Zoho CRM

Altcraft Profiles unify contact identity, behavioral history, channel subscriptions, and segment membership. We split Profiles into Zoho CRM Leads (for pre-qualified prospects) and Contacts (for qualified buyers attached to Accounts) based on lifecycle stage criteria defined during scoping. The original Altcraft Profile ID and lifecycle stage preserve in custom fields profile_id__c and altcraft_lifecycle__c on both Lead and Contact for audit and cross-reference.

Altcraft Company records linked to Profiles map to Zoho CRM Accounts. The Company domain becomes the Account Website field and serves as the dedupe key during import. We create the Account before Contact import so the AccountId Lookup is satisfied at insert time.

Static Altcraft Segments map to Zoho CRM Tags on the Lead and Contact records. Dynamic segments with behavioral criteria cannot map 1:1 to Zoho because Zoho lacks a real-time segment engine. We export the segment definition as a structured criteria document and recommend Zoho Custom Filters or Saved Views as the equivalent lookup method in Zoho CRM.

Altcraft Scenarios include conditional branching, loop constructs, and API webhook calls that have no standard export format. We do not migrate Scenarios as automation logic. We deliver a written inventory of every active Scenario with its trigger, conditions, actions, and a recommended Zoho Workflow Rule and Blueprint equivalent. The customer's admin rebuilds the automation in Zoho post-migration.

Altcraft Campaign records (send history, open and click analytics, channel assignment) map to Zoho CRM Campaigns. Campaign status, type, and budget data migrate directly. Engagement metrics (opens, clicks) transfer as custom fields because Zoho Campaign standard fields track member response differently than Altcraft's behavioral attribution.

Altcraft templates export in standard HTML and plain text formats. A/B test variants preserve as separate templates with naming convention prefix (e.g., A_, B_). We map template subject and body fields to Zoho Email Template Subject and Content fields.

Altcraft Products and SKU data map to Zoho CRM Products. ProductCode migrates from Altcraft sku field. Standard pricing list entries create in Zoho Products during import.

Altcraft Order history linked to Profiles maps to Zoho Quotes if the customer's Zoho edition includes the Quotes module. If Quote is unavailable or the order data is transactional, we propose a custom Orders module built in Zoho Extensions to preserve order history tied to the Account.

Altcraft Control Groups assign holdout percentages for campaign analytics. We preserve Control Group membership as a custom field on the Profile before export, then map to altcraft_control_group__c on Zoho Lead and Contact. Zoho Campaign member tracking serves as the replacement for ongoing campaign holdout analysis.

Altcraft loyalty tiers and promo code pools tie to Profile records. We export loyalty tier (gold, silver, bronze, etc.) as a picklist field and promo code pools as text or multi-select fields. Recreation in Zoho depends on whether the customer licenses Zoho Loyalty or builds equivalent logic in custom fields.

Altcraft user-defined fields on the Profile object export as structured columns in the Profile CSV. We map each to a Zoho CRM custom field of the equivalent data type (text, date, numeric, picklist, multi-select). Zoho's limit is 300 custom fields per module; we flag any mappings exceeding that threshold during scoping.

Altcraft Form definitions and NPS question structures export cleanly. Response data already embedded in Profile records migrates as standard field data. Standalone form response logs transfer as a related data object mapped to Zoho Notes or a custom module. Form rebuild recommendation is Zoho Forms or the customer's web team.