Migrate from YetiForce CRM to Zoho CRM

YetiForce Organization records map directly to Zoho CRM Accounts. Organization fields (company name, website, industry, type, address) migrate to standard Zoho Account fields. We create Accounts before any Contact or Potential import to satisfy lookup dependencies. The Organization record ID from YetiForce is held in a staging column for cross-reference during child-record migration.

YetiForce Contact records map to Zoho Contacts with name, email, phone, mailing address, and assigned owner preserved. The related Organization reference resolves to the Zoho Account via the Organization-to-Account mapping completed in the prior step. We use the Contact email address as the dedupe key during Zoho import to avoid duplicate record creation.

YetiForce Lead records (pre-conversion prospect data) map to Zoho Leads. Lead_Source and Lead_Status from YetiForce migrate to Zoho Lead Source and Lead Status picklist fields. We flag any Leads with an existing Contact email in the migration scope for the customer's admin to review before final import.

YetiForce Potentials map to Zoho Deals. The Potential stage name maps to a Zoho Stage value via a configuration table built during scoping, as stage names differ between YetiForce instances. The related Organization reference resolves to the mapped Account. Potential amount, closing date, and sales pipeline assignment migrate to Zoho Deal fields. We pre-create the Zoho pipeline and stage values if they do not already exist in the destination account.

YetiForce Project records map to Zoho Projects. Project name, status, start date, end date, and assigned owner migrate to standard Zoho Project fields. Custom fields on YetiForce Projects (tree picklists, reference fields) require type-aware mapping — tree picklist values are flattened to text fields in Zoho if the destination module has no equivalent tree structure. We pre-create any missing custom fields against Zoho's 300-field module limit before migration begins.

YetiForce Project Tasks link to a parent Project and include subject, status, priority, and assigned user. Task status and priority picklist values transform to Zoho Task status and priority via the configuration table. The parent Project ID from YetiForce resolves to the Zoho Project record ID via the Project mapping step. Zoho Tasks are linked to the Project via the WhatId field.

YetiForce Tickets map to Zoho Cases. Ticket title, status, priority, and category migrate to Zoho Case Subject, Status, Priority, and custom category fields. Related Contact and Organization references resolve to their mapped Zoho Contact and Account records. Custom ticket fields in YetiForce require pre-creation in Zoho as custom fields before migration.

YetiForce Products (name, unit price, vendor link, description, stock levels) map to Zoho Products. The vendor reference resolves to the migrated Vendor record by matching on vendor name. Stock quantity maps to Zoho Product Quantity in Stock. We migrate Products before Potentials if Products are linked as line items, to satisfy any Product lookup in the Deals module.

YetiForce Vendor records (company name, website, address, assigned owner) map to Zoho Vendors. Vendors migrate before Products to preserve the foreign-key relationship between the two modules. The vendor name becomes the dedupe key during import.

YetiForce User records carry login, name, role, and preference data. Direct user-to-user migration is not supported since Zoho User provisioning requires admin action in the destination account. We map Users to Zoho by matching email address and flag any YetiForce owner referenced on a record without a matching Zoho User in a reconciliation queue for the customer's admin to provision before the migration phase begins.