Migrate your Wetroo CRM data

Leads are the primary intake object in Wetroo. All tiers offer unlimited lead management. We migrate Leads 1:1, preserving source attribution (Facebook, Google, manual), custom field values, and the assigned team/owner mapping. Webhook-created leads carry a source tag we preserve as a property.

Contacts are distinct from Leads and are the enriched record after a lead has been qualified. We migrate Contacts with full contact details, phone numbers, email addresses, and lifecycle stage. Custom contact properties are mapped to destination fields or held as custom fields.

Companies are Wetroo's account-level object linking multiple Contacts and Deals. Company names, industry tags, and custom fields migrate directly. Address and billing data may require field-level mapping depending on the destination schema.

Deals are tied to Companies and Contacts with a stage value. We preserve stage order, deal value, expected close date, and owner assignment. Pipeline-level custom stages are mapped to the destination pipeline or recreated.

Activities include call logs, WhatsApp messages, emails, and notes. Call activity via OBD is captured via the /api/v1/?apirequest=obd_record endpoint. WhatsApp message threads are accessible via the conversation API. We map activities to the destination activity model and flag any conversation threads that may need manual export.

Tasks and calendar Events are supported. We export task records with due dates, assignees, and status. Event records (meetings, appointments) migrate with attendee data. Automated reminders tied to Wetroo workflows do not carry over.

Pipelines and their stages are configurable per account. We read the pipeline configuration via API and map it to the destination pipeline structure. Stage names and order are preserved; any stage-specific automation is flagged as non-migratable.

Custom fields on Leads, Contacts, and Deals are supported. We map named custom fields to equivalent destination fields where a match exists. Fields with picklist or multi-select values require value-level mapping. We alert on any custom field with no clear destination mapping.

Drip marketing sequences and automated cadences are Wetroo automation-layer objects with no portable schema and no API endpoint to export sequence definitions or step logic. We do not migrate drip sequences. We advise rebuilding them in the destination CRM using exported contact lists as the audience.

WhatsApp message history is accessible via Wetroo's conversation API. We extract message content, timestamps, sender/receiver, and media attachments where supported. Note that media files may require separate download and re-attachment in the destination.

Integrations with third-party platforms (payment gateways, accounting tools, shipping solutions, affiliate trackers) are configuration-level settings that do not live in Wetroo's data model. We do not migrate integration credentials or connection configurations. We export the data that flowed through those integrations separately.

User records with name, email, role, and team assignment migrate. Team structures and sub-teams are mapped to the destination's user hierarchy. Note that Wetroo enforces per-user seat limits per plan tier — migrating more users than the destination tier allows will require a seat upgrade.