Migrate from Wetroo CRM to Twenty CRM

Wetroo Leads (primary intake object with source attribution from Facebook Lead Forms, Google Data Extractor, or manual entry) map to Twenty People records. We preserve the lead source as a custom field or tag in Twenty. Any lead status field (qualified, unqualified, follow-up) migrates as a custom picklist field. If the Wetroo account has already converted some Leads to Contacts, we treat Contacts as the canonical People record and do not duplicate from Lead.

Wetroo Contacts (enriched records after lead qualification) map directly to Twenty People. Phone numbers, email addresses, lifecycle stage, and custom field values migrate. Note that Twenty's standard People fields are minimal out of the box — per GitHub issue #13953, Twenty ships without industry-standard fields like jobTitle, department, and website as standard fields; we create these as custom fields in Settings → Data Model before import.

Wetroo Companies (account-level objects linking Contacts and Deals) map to Twenty Companies. Company names, industry tags, address, and billing data migrate. Custom fields on Companies require pre-creation in Twenty's Data Model before import. The Company object is created in Twenty before People import so that the People-to-Company relation is satisfied at insert time.

Wetroo Deals tied to Companies and Contacts with a stage value map to Twenty Opportunities. We preserve deal value, expected close date, stage name, and owner assignment. Pipeline stages map to Twenty's Opportunity stage values, and we configure the pipeline view (Kanban) to match Wetroo's stage ordering.

Wetroo pipeline configuration (stages, stage order, probability values) reads from Wetroo's API and maps to Twenty's Opportunity pipeline view. We configure stage names and probabilities in Twenty before importing Opportunities. Any custom stage-level fields (stage-specific required fields) require pre-creation in Twenty Data Model.

Wetroo OBD (outbound dialer) call records are accessible via the /api/v1/?apirequest=obd_record endpoint. We extract call duration, disposition, timestamp, and linked Contact. These map to Twenty Task records with a call subtype tag. Owner assignment resolves by email match against Twenty Users.

Wetroo notes attached to Leads, Contacts, Companies, or Deals map to Twenty Note records linked to the corresponding People, Company, or Opportunity via Twenty's relation system. Rich text formatting is preserved where Wetroo's export format supports it.

WhatsApp conversation threads are accessible via Wetroo's conversation API. We extract message content, timestamps, sender and receiver, and media attachment references. Media files download separately and are re-attached in Twenty. Message threads attach to the corresponding People record. Note that this adds an extraction step beyond the standard CSV workflow and affects timeline estimates for high-volume WhatsApp accounts.

Wetroo Tasks and calendar Events (meetings, appointments) migrate to Twenty Tasks. Due dates, assignee, status, and attendee data preserve. Automated reminders tied to Wetroo's automation layer do not migrate because those are automation-layer objects. Event records from Wetroo map to Twenty Tasks with a meeting subtype and location preserved.

Custom fields on Leads, Contacts, Companies, and Deals are supported for migration. We map named custom fields to equivalent custom fields created in Twenty Settings → Data Model before import. Picklist and multi-select values require value-list mapping against the destination picklist options. Fields with no match in Twenty are flagged for the customer's admin to review. Per Twenty's import documentation, fields must exist in the Data Model before CSV import begins — we create these during the schema setup phase.

Wetroo User records (name, email, role, team assignment) migrate to Twenty Members. Team structures and sub-teams map to Twenty's user hierarchy. Owner assignments on Deals and Activities resolve by email match against Twenty Members. Wetroo's seat-tier limits (20 on Business) do not constrain migration but we flag user counts against Wetroo plan tier during scoping to identify if a plan upgrade is needed before extraction.