Migrate from Wetroo to monday CRM

Wetroo Contact records (name, phone, email, custom fields) map directly to Monday.com CRM Contact objects. We extract via Wetroo API and import via Monday.com Contacts API or CSV. Phone numbers stored in Wetroo map to the Contact phone field; if Wetroo stores multiple phone types, we map them to separate Contact phone entries in Monday. Custom fields on Contact map to Monday column types (text, number, date, dropdown) scoped to the Contacts board.

Monday.com CRM does not have a native Lead object equivalent to Wetroo's Lead records. During scoping, we determine whether to model Wetroo Leads as Monday.com Organizations (recommended for qualified accounts) or as items in a dedicated pipeline board (recommended for unqualified prospects). Wetroo lead status and qualification score transfer as a dropdown or number column on the destination record. The customer chooses the model during discovery.

Wetroo Deals map to Monday.com Deals (if the customer has installed the Deals feature) or to board items with deal-specific columns (deal value, expected close date, probability). We configure the destination board with matching column types before import. Wetroo dealstage maps to the Monday Status column; pipeline assignment maps to the board Group or a dedicated pipeline board.

Wetroo pipeline stages (which are customer-defined and tied to WhatsApp workflow triggers) map to Monday.com Groups or Status column values on the destination board. Stage sequence order is preserved and set explicitly in Monday so that items display in the correct stage order. Any stages with no Monday equivalent are flagged during scoping and mapped to an 'Other' status value with the original stage name stored as a text column.

Wetroo Company records map directly to Monday.com CRM Organization objects. Organization name, domain, address, and custom fields transfer. We set Organization as the parent record before Contact import so that the Organization lookup is satisfied at the time of Contact insert.

Wetroo custom fields on Contacts, Leads, and Deals map to Monday.com column types. Text properties become text columns; numbers become number columns; dates become date columns; dropdown options become dropdown columns; multi-select values become tag columns. Note: Monday.com custom columns are scoped per board, not shared across the workspace. If the same custom field is used across multiple Wetroo objects, it must be recreated on each destination board.

Wetroo Owner records (name and email) assigned to Deals and Leads map to Monday.com People columns on the destination board. We extract distinct owner emails from Wetroo and resolve them against Monday.com workspace members. Owners without a matching Monday.com user are held in a reconciliation queue; the customer provisions the missing users before record import resumes.

Wetroo team membership records (team name and member list per owner) export as a relational dataset. We map team names to a Monday.com Tag column and populate member assignments as tag values on the relevant board items. Teams without a Monday equivalent are created as new Tag values during import.

Wetroo automation playbooks (JSON-configured workflow triggers tied to WhatsApp events) are exported as a structured reference document listing sequence name, trigger conditions, action steps, and delays. Monday.com's automation builder uses a rule-based model with action types (change column, notify, create item) that partially overlaps with Wetroo playbooks. We deliver the playbook inventory with recommended Monday automation equivalents; the customer rebuilds automations manually post-migration.

WhatsApp conversation history and chat transcripts are stored in WhatsApp's infrastructure, not in Wetroo's database. They are not accessible via the Wetroo API or any export mechanism. We preserve all structured records (Contacts, Leads, Deals) that originated from WhatsApp conversations, but the conversation threads themselves must be retained in WhatsApp. Customers should export critical chat history directly from WhatsApp before the migration cutover if a conversation record is required.