Migrate from YetiForce CRM to Freshsales

YetiForce Organization records map directly to Freshsales Accounts. Organization name, address, industry, type, website, and assigned owner migrate to Freshsales Account fields. We import Accounts first in all migration phases because Contact records require an AccountId lookup reference to satisfy the relationship. Organization website is preserved for Freshsales's automatic domain-based Account creation logic if the customer enables it post-migration.

YetiForce Contact records map to Freshsales Contacts with name, email, phone, address, and assigned owner preserved. The Organization relationship maps to Freshsales AccountId via a lookup resolved at migration time using Organization record IDs from Phase 1. YetiForce's per-instance custom field IDs (cf_123, cf_456) are resolved against the dynamic schema map built during the audit phase, then mapped to typed Freshsales custom fields.

YetiForce Lead records migrate to Freshsales Lead with Lead_Source and Lead_Status preserved as custom fields in Freshsales if those values do not map directly to Freshsales standard picklists. The split between pre-conversion Leads and post-conversion Contacts is preserved—Leads in YetiForce that have not been converted stay as Freshsales Leads until the customer's sales team works through them post-migration.

YetiForce Potentials map to Freshsales Deals. The Potential's related Organization becomes the Deal's Account lookup. Potential stage names (Probability, Lost, Won, etc.) map to Freshsales pipeline stage values via a customer-supplied configuration table during scoping. Amount, Expected Close Date, Sales Stage, and Description migrate directly. We create the Freshsales pipeline before migration so that Deals land in the correct pipeline at import time.

YetiForce Projects have no native Freshsales equivalent. We map Projects to Freshsales Tasks with a custom Project Name field linking related tasks, or we create a Freshsales Custom Object named Project for customers that need project-level record tracking. The customer chooses the strategy during scoping. Project status (Active, Completed, On Hold) translates to Task status (Open, Completed, Deferred) or a custom picklist on the Project custom object.

YetiForce Project Tasks link to a parent Project via a reference field. We map Project Tasks to Freshsales Tasks with a custom Parent_Project__c field storing the source Project ID so that the relationship is preserved for reporting. Task subject, status, priority, assigned user, start date, and end date migrate directly. Priority picklist values map via the configuration table.

YetiForce Tickets have no direct Freshsales equivalent unless the customer licenses Freshdesk for support. We map Tickets to Freshsales Deals with a ticket-type pipeline (a dedicated Deal pipeline scoped to support tickets) or to Tasks with custom Ticket fields. Ticket status, priority, category, and related Contact and Organization references migrate with field-level mapping. The customer chooses the ticket strategy during scoping.

YetiForce Products (name, unit price, vendor link, description, stock levels) map to Freshsales Products. The vendor reference resolves to the migrated Vendor record by matching on vendor name. Unit price, product description, and stock information migrate directly. Products must be imported before Deals that reference them via line items.

YetiForce Services (recurring offerings with price per unit and description) share the same data shape as Products. We map Services to Freshsales Products with a custom is_service__c flag set to true so that the customer's team can distinguish recurring offerings from one-time products in reporting.

YetiForce Vendor records map to Freshsales Accounts with a custom vendor_flag__c checkbox set to true. Vendor name, website, address, and assigned owner migrate directly. Vendor records are imported before Products to preserve the foreign-key relationship. The customer may alternatively choose to import Vendors as Contacts in a separate phase if vendor-level reporting should not mix with customer Account records.