Migrate from Efficy CRM to Zoho CRM

Efficy Company records map to Zoho CRM Account. The Company Name becomes Account Name; industry, website, and address fields map to their Zoho equivalents. We load Accounts first because every Contact and Deal in Zoho carries a lookup to Account. Efficy's multi-address support maps to Zoho's Address fields using the primary address values at migration time.

Efficy Contact records map directly to Zoho CRM Contact. First name, last name, email, phone, title, and department migrate. The Efficy Company linkage (foreign key to Company) maps to Zoho's Account Name lookup. Multi-address support from Efficy maps to Zoho's Address fields. We resolve any orphaned Contacts (linkage to a Company that failed import) before the Contact batch commits.

Efficy Opportunity records map to Zoho CRM Deal. The opportunity name becomes Deal Name, amount maps to Deal Amount, close date maps to Closing Date, and stage maps to Stage. Efficy's pipeline assignment maps to Zoho's pipeline field. We validate that the Account lookup resolves before Deal insert. Closed-Lost and Closed-Won reasons from Efficy custom fields become Zoho Deal custom fields.

Each Efficy pipeline with its stage values maps to a Zoho pipeline with corresponding stage names. We configure the Zoho pipeline structure before migration begins. Stage probability percentages migrate as Zoho probability values. Efficy stage colours do not transfer; we document the original colour mapping for the customer's admin to re-apply in Zoho.

Efficy call activities map to Zoho Task records with Call set as the activity type. Call duration, disposition, and outcome from Efficy custom fields map to Zoho Task custom fields. We preserve the parent linkage (Contact or Opportunity) via Zoho's SE Module and SE ID fields. Activity timestamps migrate as Activity Date.

Efficy email activity records map to Zoho Task records with Email as the activity type. Email subject, body, and direction (sent/received) migrate to Zoho Task fields. Parent linkage to Contact or Opportunity is preserved via Zoho's related-to fields. Email attachments migrate as Zoho attachments linked to the Task.

Efficy meeting activities map to Zoho Event records. Start time, end time, location, and description migrate. Attendee information from Efficy maps to Zoho Event attendees. We link the Event to the parent Contact or Opportunity via Zoho's related-to fields at migration time.

Efficy task activities map to Zoho Task records (non-call, non-email type). Status, priority, due date, and description migrate. Task ownership migrates by resolving the Efficy owner email to a Zoho User. Reminder settings from Efficy map to Zoho Task reminder fields.

Efficy's native project module (Kanban boards, milestones, resource management) has no direct Zoho CRM equivalent. We assess the customer's project complexity during scoping. Simple projects migrate as a custom Zoho CRM module with Project Name, Status, Due Date, and Assigned To fields. Complex projects with milestones and dependencies require Zoho Projects (a separate application) or a third-party integration plan; we flag this and document the structure for the customer to decide before migration.

Efficy Ticket records map to Zoho CRM Case. Subject, description, status, priority, and agent assignment migrate. Efficy ticket pipelines map to Zoho Case categories or a custom field. Conversation history migrates as threaded Case comments. We validate that the contact lookup resolves before Case insert.

Efficy custom fields on Companies, Contacts, Opportunities, and Tickets map to Zoho CRM custom fields of equivalent type (text, picklist, date, numeric, checkbox). We extract the full Efficy field schema per object during discovery, then pre-create the Zoho custom field schema in a sandbox before production migration. Field validation rules (required, format) require Zoho admin configuration post-migration.

Efficy User records map to Zoho CRM User by email match. User name, role, and active status migrate. Inactive Efficy users are excluded from the user count mapping but their historical record assignments are preserved as custom fields pointing to the original user name. Active Zoho users must be provisioned before Contact and Deal migration begins because Owner assignment is required.

Efficy documents attached to Companies, Contacts, or Opportunities migrate as Zoho CRM attachments linked to the corresponding record. Documents without a download URL are flagged in the migration report and escalated to the customer for manual retrieval. We preserve the original file name and MIME type.

Efficy tags on Companies, Contacts, and Opportunities map to Zoho CRM Tags. Multi-tag assignments on a single record flatten to Zoho's tag format. Tags used for segmentation migrate as Tags; tags used for classification migrate to Zoho custom picklist fields at the customer's discretion.

Efficy automation rules, workflow triggers, and follow-up sequences do not export via the API or Import Wizard. We document every active automation during discovery with its trigger, conditions, actions, and recommended Zoho Workflow Rule or Blueprint equivalent. The customer receives a rebuild specification ordered by revenue impact priority. We do not rebuild automations inside the migration scope.