Migrate from Moskit to Zoho CRM

Moskit Contact records map directly to Zoho CRM Contact. Standard fields (Full Name, Email, Phone, Mobile) transfer with direct type matching. The Contact-to-Company link in Moskit maps to Zoho's Accounts lookup on Contact; Accounts must be imported first so the lookup relationship is satisfied at insert time. Any Moskit Contact without a linked Company becomes a standalone Zoho Contact with no AccountId, which is valid in Zoho but flagged in the scoping report for the customer to decide on Account assignment.

Moskit Company records map to Zoho CRM Account. The company name becomes Account Name; address fields map to Shipping Address and Billing Address. Moskit's custom Company fields (industry classification, employee count, revenue tier) transfer to matching or newly created Zoho custom fields. Zoho enforces 300 fields per module; we audit Moskit's total custom field count on Companies during discovery and flag any that exceed the destination limit before import begins.

Moskit Deal records map to Zoho CRM Deal. Deal Name, Amount, Closing Date, Owner, and Stage transfer directly. The Moskit pipeline stage name maps to a Zoho Stage value that we configure during schema setup. Moskit's loss reason and win reason custom fields become Zoho custom picklist fields. Closed-Loss and Closed-Won dates from Moskit transfer as Zoho Deal fields if present. Deals are imported before Projects to establish the deal IDs needed for the project-to-deal lookup remapping in the second pass.

Moskit's custom-named pipeline stages (e.g., 'Qualificação', 'Proposta', 'Fechado Ganho') map to Zoho Deal Stage values. We configure the stage names, stage order, and probability percentages during the Zoho CRM Deal layout setup before any Deal records import. Stage-level probability migrates from Moskit to Zoho's stage probability field.

Moskit Activities encompass tasks, calls, meetings, and notes. We split them during transform: task-type activities map to Zoho Task; meeting-type activities map to Zoho Event; call-type activities map to Zoho Task with Task Subtype set to Call and Call Duration captured. The activity's linked Deal or Contact reference becomes the WhatId or WhoId on the Zoho record. Activity owner maps to Zoho User by email match.

Moskit Projects do not have a direct standard Zoho CRM equivalent. We create a Zoho Custom Module named 'Projects' and add a lookup field referencing the Deals module. Projects are imported in a second pass after Deals are confirmed in Zoho. We capture the Moskit project-to-deal reference during extraction, then inject the corresponding Zoho Deal ID during the Projects import pass. This two-pass approach is required because the deal reference must resolve at migration time, not at extraction time.

Moskit custom fields on Contacts, Companies, Deals, and Activities require individual object-level schema queries because the API does not expose a bulk custom field definition endpoint. We query each object type separately, retrieve its custom field definitions (name, type, picklist values), and map them to Zoho custom fields of the closest equivalent type. Text, number, date, and picklist types map cleanly. Multi-checkbox picklists in Moskit map to Zoho multi-select picklists. Any custom field exceeding Zoho's 300-field module limit is flagged during scoping and the customer decides which fields to retire before migration.

Moskit User records (name, email, role) map to Zoho CRM Users. We resolve owners by email match. Any Moskit User without a matching Zoho User goes to a reconciliation queue for the customer's Zoho admin to provision before record import resumes. Inactive Moskit users are imported with an inactive flag so they can be set correctly in the destination. User role names in Moskit do not map to Zoho role names; we preserve the role name in a custom field for the admin to reassign during Zoho setup.

Moskit's WhatsApp Business sync stores conversation metadata (last message timestamp, participant count, message count, linked WhatsApp number) linked to Contact records. The actual message content lives in WhatsApp's infrastructure and is not accessible via Moskit's API. We import the available metadata into Zoho Contact custom fields and flag the message content gap in the scoping report so the customer can decide whether to export WhatsApp data separately via WhatsApp Business API or a dedicated WhatsApp data export tool.

Moskit contact and deal tags stored as multi-value label fields map to Zoho multi-select picklist fields on the respective modules. We extract unique tag values, create corresponding picklist options in Zoho, and populate the fields during record import. If a record has more tag values than Zoho's multi-select character limit allows, we truncate and flag the affected records.