Migrate from Getfly CRM to Zoho CRM

Getfly's Account object holds both organization-level data (company name, address, industry) and individual contact data (contact name, phone, email) in a single record. We split each Getfly Account into a Zoho Account (Company module) for the organization and a Zoho Contact for the primary individual. Any secondary contacts stored in Getfly as additional field entries become separate Zoho Contact records linked to the same Account. The original Getfly Account ID is preserved in a custom Zoho text field getfly_account_id__c for cross-reference during the parallel-run period.

Getfly Products map directly to Zoho Products with SKU, unit price, and product details preserved. Getfly's detail_custom_fields nested object maps to custom fields on the Zoho Product record, which we pre-create before migration based on the field audit from Getfly's admin panel. Product code (SKU) becomes the Zoho Product Code field and is used as the deduplication key during import.

Getfly's configurable pipeline stages are customer-specific in name and order. We extract the full stage configuration during the discovery audit, then create a Zoho custom Status picklist with each Getfly stage name mapped to an equivalent Zoho Status value. Stage order and any probability or forecast flags in Getfly become custom numeric fields on the Zoho Deal.

Getfly Deal records map to Zoho Potentials (commonly called Deals). Each Deal is linked to the Zoho Account resolved from the Account split in step 1. Deal amount, close date, owner (resolved via email lookup to Zoho Users), and stage (mapped via the Status picklist from step 3) transfer directly. If Getfly stores deal-to-product associations, those map to Zoho Potential Products during import.

Getfly Activity records include type, date, duration, owner assignment, and linked account. Activity type determines the Zoho target: tasks become Zoho Tasks, meetings become Zoho Events with Start DateTime and End DateTime preserved. The linked Getfly Account resolves to the Zoho Account-Contact pair from step 1, and the owner resolves via email-based lookup to Zoho Users. Duration and disposition data transfer to Zoho custom fields if not natively supported.

Getfly PABX call records include call direction, duration, and recording URL. Call logs migrate as Zoho Tasks with a Call disposition custom field. Recording URLs are time-limited or signed links returned by Getfly's API, so we download all recording audio files at export time and re-upload to Zoho's file storage, attaching the re-hosted recording to the corresponding Task. If Zoho's telephony integration is configured post-migration, call recording continuity is preserved without broken links.

Getfly Users acting as record owners are resolved by email match against Zoho Users. We export the full Getfly user roster during scoping and match each hubspot_owner_id-equivalent to a Zoho User by email address. Any Getfly owner without a matching Zoho User account goes to a reconciliation queue for the customer's admin to provision before Deal and Activity imports begin.

Attachments associated with Getfly Accounts, Products, or Deals are referenced by URL in the API. We download files to local storage during export, preserving original filenames and mime types, then re-upload to Zoho's file attachment system using the Zoho Files API. Each file is linked to the target record (Account, Contact, Product, or Deal) via the Zoho attachment endpoint after the parent record has been created.

Getfly Marketing campaigns track name, start and end dates, and linked Accounts. Campaign membership (which Accounts were contacted) migrates as Zoho Campaign Members linked to the Zoho Campaign record. We preserve campaign status (Active, Completed, Planned) as Zoho Campaign Status. Any campaign-level notes or custom fields migrate to Zoho Campaign custom fields pre-created during schema setup.

Getfly supports custom fields on Accounts and Products but exposes no public schema registry endpoint. We discover custom fields by sampling Product and Account records during the export audit, then generate Zoho field definitions matching the discovered types (text, number, date, picklist). We instruct customers to run a full field audit report from Getfly's admin panel before migration kickoff to catch rarely-used fields that sampling might miss. Custom field mapping is validated in the sandbox migration before production cutover.

Getfly workflow rules are internal platform configuration with no public export endpoint. We do not migrate automations as code. During scoping, we provide a workflow audit questionnaire that the customer completes to document every active Getfly automation (trigger, conditions, actions, and affected records). We deliver this as a written inventory document with each automation mapped to an equivalent Zoho Workflow Rule or Blueprint step, which the customer's Zoho admin or a Zoho partner rebuilds post-migration. This is a separate engagement from the data migration.