Migrate from GorillaDesk to Twenty CRM

GorillaDesk customers migrate to Twenty People. First name, last name, email, phone, and job title map directly. Physical addresses (street, city, state, zip) become Twenty's structured address fields. B2B customers may also get a Company record with the business address.

GorillaDesk companies (available via API) migrate to Twenty Companies. Business name, domain/website, phone, industry, and employee count map to standard Twenty Company fields. Parent-child company relationships map to Twenty's parentCompanyId relation. If a company lacks a website, the domain field is left blank, and any notes or tags attached to the company in GorillaDesk become custom text fields on the Twenty Companies record for future reference.

GorillaDesk jobs have no native Twenty equivalent. Jobs migrate as Twenty Tasks with job-specific metadata (technician, service type, status) stored as custom fields on the Task. If a dedicated Job object is preferred, FlitStack creates one in Twenty's data model before migration and maps job records into it.

GorillaDesk stores service addresses on individual job records, not centrally on customers. Service locations migrate as address fields on the related People or Company record. If multiple service addresses exist per customer, all locations are preserved and your team decides which becomes primary.

GorillaDesk users (technicians, office staff) migrate to Twenty Workspace Members. Email matching is used to resolve owner assignments on migrated records. Unmatched users are flagged before migration so your team can create their Twenty account or reassign records. Active status and role information are preserved as custom fields to maintain organizational context after migration.

GorillaDesk invoices have no direct Twenty equivalent. Invoices migrate to a custom Invoice object created in Twenty's Settings → Data Model. Fields include invoice number, amount, date, status, and linked customer reference. If a custom object isn't desired, invoices attach to the related People record as Tasks with custom invoice fields.

GorillaDesk estimates migrate similarly to invoices — to a custom Estimate object or as Tasks with custom estimate fields. Line items, total amount, and status are preserved. Acceptance history and timestamps migrate as custom datetime fields for audit continuity. If a custom Estimate object is used, it is defined in Twenty's Settings → Data Model prior to import to ensure field compatibility.

GorillaDesk notes attached to customers or jobs migrate to Twenty Notes, preserving the original text body, author, and creation timestamp. Notes attach to the related People, Company, or Task record in Twenty. Rich-text formatting is preserved where GorillaDesk supports it.

GorillaDesk file attachments on customers or jobs migrate to Twenty's attachment model on the equivalent record (People, Company, Task). File size limits per Twenty's hosting configuration apply. Inline images in notes are downloaded and re-hosted as attachments. All attachments retain original filenames and are linked via the standard Twenty attachment relationship, ensuring downstream access and searchability.

GorillaDesk tags on customers and jobs migrate to a custom field in Twenty. Multi-value tags map to a Twenty multi-select field if your Twenty version supports it; otherwise they collapse into a comma-separated text field for reference. You may also rename the custom field to match your internal tag naming conventions before migration.

GorillaDesk stores multiple phone numbers with types (mobile, work, home). The primary phone number migrates to Twenty's standard phone field; additional numbers and their types become custom fields on the People record. If a customer has more than three phone entries, the extras are stored as additional custom phone fields, each labeled with the original type for clarity.

GorillaDesk scheduling rules and routing automations have no Twenty equivalent. We document your GorillaDesk automation logic as a rebuild reference for Twenty's workflow builder. Scheduling and dispatch functionality requires manual reconfiguration. Your team receives a step‑by‑step automation guide with trigger events, conditions, and actions extracted from GorillaDesk, so Twenty's workflow builder can replicate the existing routing logic.