Migrate from Actito to Zoho CRM

Actito Profiles map to Zoho CRM Contact for records with an active customer relationship and to Lead for marketing-qualified or prospect records. We inspect the Profile's subscription status, last activity date, and any lifecycle stage attribute to determine the split routing. The original Actito Profile ID preserves in a custom field actito_profile_id__c for cross-reference. Entity partitioning in Actito maps to a custom picklist field actito_entity__c on the Zoho record so that org-level segmentation is preserved without requiring a separate Zoho Org.

Actito Custom Tables linked to Profiles migrate to Zoho CRM custom modules created with the _C naming convention (e.g., Contracts_C, Subscriptions_C). We inspect the table schema during scoping, map field types to Zoho field equivalents (string to varchar, date to date, integer to bigint, boolean to checkbox), and pre-create the module and its lookup relationships before data import. Foreign-key references between Custom Tables resolve via Zoho lookup fields at migration time.

Actito's entity-based licence partitioning maps to a Zoho CRM custom picklist field rather than a separate Zoho Org, unless the customer requires full data isolation between entities. We create the actito_entity__c picklist with the entity names from Actito, apply it to the Contact and Lead modules, and configure Zoho CRM data sharing rules to restrict record visibility by entity value.

Actito campaign configurations (name, schedule, targeting criteria, channel references) migrate as Zoho CRM Campaign records with channel type and status preserved. The actual campaign content (email templates, SMS bodies, push copy) migrates as attachment records or Notes linked to the Campaign for the customer's marketing team to rebuild and activate. Active campaign send status cannot be preserved in Zoho because campaign execution state is platform-specific.

Actito Scenarios (event-triggered automation workflows) do not have a direct Zoho CRM equivalent because Scenarios use a different event model from Zoho Workflow Rules. We map scenario trigger conditions, branching rules, and action steps into a written inventory document with Zoho Workflow Rule and Deluge script equivalents. The customer's admin rebuilds the automation logic in Zoho using that document as the specification.

Actito email sender configurations (From name, From address, DKIM status, SPF record) migrate as a Zoho Email Channel setup with a flag to reconfigure DNS records (DKIM, SPF, return-path) on Zoho's mail infrastructure. We document the Actito sender settings during discovery and provide the Zoho DNS configuration values so the customer's IT team can complete the authentication before campaign send.

Actito SMS sender configurations and sender IDs migrate as Zoho SMS channel records. If Actito uses a specific SMS aggregator (e.g., Twilio, MessageBird), we document the provider and recommend the Zoho-native SMS integration or Deluge-based API connector to re-establish SMS send capability.

Profile-level opt-in and preference data migrates to Zoho Contact as standard fields (HasOptedOutOfEmail, Do Not Call) and custom fields for Actito-specific preference attributes. Double opt-in status migrates to a custom field actito_double_optin__c. Channel-level consent flags (email, SMS, push) map to Zoho's corresponding opt-out fields with the logic inverted (Actito opt-in true becomes HasOptedOutOfEmail false).

Actito ETL export job definitions (file naming patterns, scheduling, compression type) are documented as Zoho scheduled export configurations. We note the original Actito export schedules so the customer can recreate equivalent automated exports in Zoho Reports or via Deluge scheduled functions.

Actito webhook subscriptions and ETL job definitions migrate as documentation records listing the webhook URL, event trigger, and payload structure. Since webhook target URLs and ETL credentials are destination-specific, we flag end-point changes required and provide the Zoho webhook registration format for the customer's admin to reconfigure post-migration.

Interaction events (opens, clicks, bounces, unsubscribes) generated by Actito's campaign execution platform are not available for programmatic export via the standard API. We do not migrate these records. We recommend exporting and archiving all Actito campaign reports before cutover for historical reference; post-migration campaign performance reporting references Zoho data only from the go-live date.

Actito web tracking goals and behavioral event definitions migrate as Zoho CRM custom field records and Analytics configuration notes. Goal names, trigger conditions, and associated profile attributes map to Zoho custom fields and Zoho Analytics (or Zoho Reports) goal configurations. Actual behavioral event history does not transfer because it is generated by Actito's tracking script.