Migrate from CaseManager to Zoho CRM

Case-to-Deal routing requires manual decision at migration time

CaseManager's case records can represent sales opportunities, support tickets, or project milestones depending on your team's use. Zoho CRM separates Leads, Contacts, Accounts, Deals, and Cases into distinct modules — there is no single 'case' equivalent. We assess your CaseManager export during discovery to determine whether cases route to Zoho Deals (for sales cycles) or the Cases module (for service workflows). If your CaseManager holds a mix of both types, we create separate migration batches and map status values differently per batch. The routing decision affects pipeline stage values, required fields, and which Zoho module the records land in — get this wrong and your Zoho reporting will be split across modules unexpectedly.

Zoho CRM API credit limits throttle bulk imports at higher tiers

Zoho CRM deducts API credits per operation based on your subscription tier: Standard plans have limited daily API credits, while Enterprise and Ultimate tiers provide higher limits but still cap concurrent requests. During a large migration (25,000+ records), we batch records into chunks and pace API calls to avoid hitting rate limits. If your CaseManager export contains more than 50,000 activity log records, we split the activity migration into multiple batches spread across 24-hour windows. Exceeding Zoho's API credit ceiling mid-migration returns HTTP 429 errors and rolls back the batch — we monitor credit usage headers (X-API-CREDITS-REMAINING) and throttle proactively.

Custom field creation in Zoho CRM must precede data load

CaseManager custom fields on cases, contacts, or companies have no automatic equivalent in Zoho CRM — each requires manual field creation in Zoho's Settings before our migration tool can write data into them. We generate a field creation checklist with API field names, data types, and pick-list values during the planning phase. If your CaseManager export contains multi-select picklists, Zoho CRM's Professional tier supports multi-select picklists; lower tiers may need these converted to text fields. Skipping this step causes custom field data to drop during the import with no error until post-migration reconciliation.

Owner resolution by email match leaves orphaned records if Zoho users are not provisioned

Zoho CRM requires a valid user lookup for the Owner field on all records. We resolve CaseManager assigned_to values by matching against Zoho CRM user email addresses. If a CaseManager user has no corresponding Zoho CRM user at migration time, their records are flagged and held in a staging batch. If your admin assigns those records to a fallback owner after migration, the original ownership history is lost. We recommend provisioning all active CaseManager users in Zoho CRM before the migration run, or accepting that some historical owner assignments will be reassigned to the fallback user chosen at migration time.

Attachment re-upload does not preserve CaseManager sharing permissions

CaseManager file attachments are re-downloaded and re-uploaded to Zoho CRM's file storage. Zoho CRM files inherit the sharing rules of the parent record and the Zoho user's default sharing settings — there is no mechanism to translate CaseManager's per-file sharing permissions into Zoho equivalents. Confidential attachments that were restricted to specific CaseManager users become accessible according to Zoho's standard file sharing model post-migration. We flag files with non-standard sharing configurations during the pre-migration audit so your admin can set Zoho sharing rules before go-live.