Migrate from Acumen to Zoho CRM

Acumen person records with email addresses and job titles map directly to Zoho CRM Contacts. The record's email address becomes the unique identifier used for duplicate detection during import. If Acumen stores a person without an email, we flag that record for manual review before migration.

Acumen person records that lack an email address or have only anonymous usage data route to Zoho CRM Leads rather than Contacts. This prevents Zoho from rejecting import rows due to missing mandatory Contact fields. You specify whether to treat anonymous Acumen users as Leads or exclude them from the migration entirely.

Acumen organization records map 1:1 to Zoho CRM Accounts. The organization name becomes Account Name. Domain or website data maps to the Account Website field. Acumen organization hierarchies (parent-child) map to the Account ParentId field in Zoho — the parent must be migrated first to satisfy the lookup dependency.

Acumen deal records with a deal name, amount, and stage map to Zoho CRM Deals. Stage names from Acumen may not match Zoho's default stage pick-list — we create a value-mapping table during discovery and apply stage names exactly as they exist in Acumen. Closed-won and closed-lost statuses carry over with their original close dates.

Acumen's proprietary engagement_score field has no native equivalent in Zoho CRM. We create a custom numeric field on the Contact and Lead modules in Zoho named Engagement_Score__c. This preserves the numeric value for historical reference, but reporting on engagement trends in Zoho requires rebuilding charts or dashboards manually.

Acumen burnout_risk field captures risk categories such as Low, Medium, or High. These map to a custom pick-list field (Burnout_Risk__c) in Zoho CRM. Value mapping is performed against Acumen's exact risk-category names. Note: this field has no Zoho-native reporting context — it is reference data only.

Acumen activity records that represent tasks or call logs migrate to Zoho CRM Tasks. Subject, description, due date, status, and priority map directly. Original timestamps and owner assignments are preserved via custom datetime fields. If Acumen stores call duration or outcome, we map those to custom fields on the Zoho Task.

Acumen calendar entries or meeting records migrate to Zoho CRM Events with start time, end time, subject, location, and description preserved. The Event's link to the parent Contact or Account is reconstructed using email-based lookup. Recurring event patterns from Acumen flatten into individual Zoho Event records.

Acumen note content maps to Zoho CRM Notes. The note body migrates as the Note content field. Parent record linkage (which contact or account the note belongs to) is resolved via email match against Zoho Contacts and Accounts. Rich-text formatting is preserved where the export format allows.

Acumen custom objects migrate to Zoho CRM custom modules. We create a new Zoho module per Acumen custom object using the module API. Field types are matched (text → single-line text, number → numeric, pick-list → pick-list). N:N relationships between custom objects map to Zoho linking modules, which we create as part of the schema setup.

Acumen file attachments are re-uploaded to Zoho CRM Attachments linked to the corresponding record. File size is validated against Zoho's per-attachment limits. Files attached to non-migrated records are held in a staging bucket until the parent record lands in Zoho, then linked. Files without a parent record are linked to a default organization.

Acumen user records are resolved against Zoho CRM users by email address match. Matched users become the OwnerId on migrated records. Unmatched Acumen users are flagged before migration — your team either creates Zoho users for them first or assigns their records to a designated fallback owner. Owner resolution is validated in the sample migration before the full run.