Migrate from Moskit to Freshsales

Moskit's Contact object holds all person records regardless of qualification stage. We split on a Moskit lifecycle property if present (e.g., qualified lead maps to Freshsales Contact attached to an Account; unqualified maps to Freshsales Lead). If Moskit has no lifecycle field, all Contacts import as Freshsales Leads and the customer decides on a conversion day. We preserve the original Moskit contact ID in a custom field moskit_original_id__c on both Lead and Contact for audit and cross-reference.

Moskit Companies map directly to Freshsales Accounts. The company domain_name or website field becomes the Account Website. Account is created before any Contact or Lead import so that the Account Lookup relationship is satisfied at insert time. If Moskit stores multiple contacts per company, each Contact record in Freshsales points to the same Account via the AccountID lookup.

Moskit Deals map to Freshsales Deals. Pipeline stages from Moskit become Freshsales Deal stages, which we configure in the destination Admin Settings before migration. Deal amount, close date, owner, and custom fields migrate directly. The Moskit deal ID is preserved in a custom field moskit_original_id__c on the Deal for cross-referencing.

Moskit Projects are deal-centric and carry a reference to the originating Deal. We import Deals first, capture source IDs, then import Projects in a second pass remapping the deal reference to the new destination deal IDs. If the customer wants standalone project records, we create a Freshsales custom object called Project with a Lookup to Deal and migrate task-level details (titles, due dates, assignees) as child task records. This requires Freshsales Enterprise plan for custom objects.

Moskit Activities (tasks, calls, meetings, notes) map to Freshsales Tasks and Events. We classify by Moskit activity type: task activities map to Freshsales Task, call activities map to Task with subtype=Call, meeting activities map to Freshsales Event. Each activity's parent reference (deal_id or contact_id) is remapped to the Freshsales Deal or Contact ID resolved from the migration ID map. Timestamps and owner assignments migrate directly.

Moskit allows custom fields on Contacts, Companies, Deals, and Activities. We query each object type individually to discover its custom field schema (Moskit has no bulk schema endpoint). Each custom field is recreated in Freshsales Admin Settings under the corresponding module (Leads, Contacts, Accounts, Deals), matching field type: text to text, number to number, date to date, picklist to dropdown. Picklist values from Moskit migrate as Freshsales dropdown options verbatim.

Moskit pipeline stages (with stage order and probability if set) become Freshsales Deal stages under Admin Settings. We create each stage name matching the Portuguese label from Moskit and set the probability percentage if Moskit has that data. Stage order sequence is preserved. The customer may rename stages post-migration to English if preferred.

Moskit User records (name, email, role, active/inactive status) map to Freshsales User records. We match by email address. Active users in Moskit become active Freshsales users; inactive users are created with inactive status so the customer's admin can activate them with appropriate license assignment post-migration.

Moskit's WhatsApp sync stores conversation metadata (timestamps, participant numbers, message count) linked to Contact records, but actual message content lives in WhatsApp's infrastructure. We export the conversation metadata and create a Freshsales Note record on the corresponding Contact, with a note body indicating the conversation existed, its date range, and message count. The customer receives a separate export recommendation to pull full WhatsApp history directly from WhatsApp Business if required.