Migrate from Sercom to Zoho CRM

Zoho CRM API credit consumption during bulk migration can throttle throughput

Zoho's credit-based API system means migration throughput is gated by your edition tier. Professional grants 50,000 base credits plus 500 per user daily; Enterprise grants 50,000 base plus 1,000 per user. Bulk operations (Bulk Write API) consume 500 credits per job initiation, plus credits per record upserted (1 credit per 10 records). For a migration of 50,000 records, you may consume 5,000+ credits in bulk operations alone. We monitor credit usage via X-API-CREDITS-REMAINING headers and pace API calls to avoid 429 errors. If credits exhaust mid-migration, we pause and resume when the daily window resets (rolling 24-hour period). Teams on lower tiers (Standard, Professional) should expect longer migration windows due to credit throttling.

Lead-to-Contact conversion in Zoho CRM changes record IDs and creates new relationships

If your Sercom data includes contacts at different lifecycle stages that you want to route as Leads in Zoho, note that Zoho Lead conversion creates a new Contact record (with a new Contact ID) and links it to an Account. The original Lead record is retained but marked as 'Converted'. This means any external references (in integrations, reports, or other systems) to the original Lead ID will break after conversion. We recommend deciding before migration whether to import pre-converted records as Leads (requiring manual conversion after data lands) or as Contacts directly (preserving the original record IDs for relationship continuity). If you choose Lead import, Zoho's Convert Lead API costs 5 credits per conversion — budget accordingly for large datasets.

Custom field creation via API requires field data type to be specified and cannot be changed post-creation

When we create custom fields in Zoho CRM via POST /crm/v8/settings/fields, the data_type (text, number, picklist, multi-select, lookup, etc.) is locked after creation. A field created as a text field cannot later become a pick-list without deleting and recreating it (which risks data loss). We audit Sercom custom property types before field creation and map them to the appropriate Zoho data type. For Sercom fields storing multiple values in a text string (e.g., comma-separated tags), we create Zoho Multi-Select fields to preserve the values natively rather than storing them as a single string.

Sercom activity history (calls, emails, meetings) requires Zoho email integration to be configured first

Zoho CRM logs emails against Contact and Deal records via its email integration (Zoho Mail or external IMAP). If your Sercom account uses a different email domain or has no email logging configured, imported email records appear as Tasks with Type='Email' but without native email thread links. Meeting imports require Zoho Calendar access permissions for the migration service account. We request OAuth scopes for Zoho Calendar (ZohoCRM.events.READ, ZohoCRM.events.CREATE) during setup. Without calendar permissions, Sercom meeting records migrate as Tasks with meeting details in the description field rather than as native Zoho Events.

Zoho bulk export/import does not support Notes with rich-text attachments in CSV format

Zoho's Bulk Read API exports Notes as plain text. Any Sercom notes containing inline images, embedded links, or HTML-formatted content will lose formatting during CSV export and re-import. We extract plain text from rich-text notes and preserve the original content, but inline images download and re-upload as Zoho attachments linked to the parent record. If your Sercom notes rely heavily on rich content (tables, embedded images, hyperlinks), budget additional QA time to verify note readability post-migration. We recommend a sample note review (50 records) before committing to full volume.