Migrate from Wetroo CRM to Zoho CRM

Wetroo Leads migrate directly to Zoho Leads with full field mapping. Source attribution (Facebook Lead Form, Google Data Extractor, manual entry) is preserved in a custom field for audit. Any Wetroo custom fields on Leads map to equivalent Zoho custom fields, subject to Zoho's 300-field-per-module limit. We validate field types during scoping: picklist values from Wetroo require a matching picklist in Zoho, and multi-select fields require a multi-select picklist field type.

Wetroo Contacts (enriched records after Lead qualification) migrate to Zoho Contacts. Phone numbers, email addresses, lifecycle stage, and contact details map directly. We preserve the Wetroo contact source field and any conversion date if available. Custom fields on Contacts migrate with the same field-type validation as Leads. The Contact-to-Account linkage is resolved by matching the Wetroo Company name against the Account name we insert first.

Wetroo Companies migrate to Zoho Accounts. Company names, industry tags, address data, and billing information map directly. The Account record is inserted before any Contact migration so that the Account-Contact lookup is satisfied at Contact insert time. Wetroo custom fields on Companies map to Zoho Account custom fields.

Wetroo Deals migrate to Zoho Potentials. Deal value, expected close date, stage name, owner assignment, and associated Company and Contact links transfer directly. Stage names are mapped to Zoho Stage values during import. We pre-create the pipeline and stage structure in Zoho's Blueprint configuration before migration to ensure the stage whitelist is in place.

Wetroo's pipeline configuration is read via API and recreated in Zoho as a Blueprint with corresponding stage values. Stage order and probability percentages transfer to the Blueprint stage definition. Any stage-specific custom fields are mapped after the Blueprint is configured. This step runs before Deal migration begins.

Wetroo OBD call records are extracted via the /api/v1/?apirequest=obd_record endpoint and migrate to Zoho Tasks with Call type. Call duration, disposition, recording URL (if available), and timestamp transfer to custom Task fields. We set the Related To field on the Task to the matching Contact or Lead by email lookup.

Email activity recorded in Wetroo migrates to Zoho Tasks with email content in the description field. Subject, sender, recipient, and timestamp are preserved as Task fields. The Activity Date reflects the original Wetroo timestamp for timeline ordering. We resolve the owner and related-to record by email matching.

Wetroo Tasks with due dates and assignees migrate to Zoho Tasks. Calendar Events (meetings, appointments) migrate to Zoho Events with Start DateTime, End DateTime, and Location preserved. Event attendees are mapped to Zoho Event Relations where supported. Automated reminders tied to Wetroo's automation layer do not migrate and are flagged for manual rebuild.

WhatsApp message threads are extracted from Wetroo's conversation API as message content with timestamps, sender, and receiver. Media attachments are downloaded separately. We import the message text as Zoho Notes attached to the relevant Contact or Lead record. There is no native WhatsApp channel in Zoho CRM; the customer must re-establish WhatsApp connectivity via Zoho Flow or a third-party WhatsApp Business integration post-migration.

Wetroo custom fields on Leads, Contacts, Companies, and Deals are mapped to equivalent Zoho custom fields. We validate field types during scoping: Wetroo text fields map to Zoho single-line text, Wetroo number fields map to Zoho numeric fields, and picklist values require a matching picklist definition in Zoho. Fields exceeding Zoho's 300-field-per-module limit are flagged for consolidation or archival before migration.

Wetroo User records (name, email, role, team assignment) migrate to Zoho Users. We match by email address. Any Wetroo user without a matching Zoho User goes to a reconciliation queue for the customer to provision before record import resumes. Team structures and sub-teams are mapped to Zoho's user hierarchy.