Migrate from Inmovilla to Twenty CRM

Inmovilla contacts map 1:1 to Twenty People records. The contact's primary email, phone, job title, and address fields map to their corresponding Twenty People fields. Owner resolution uses email match against Twenty workspace members — any unmatched owner gets flagged before migration commits.

Inmovilla companies map to Twenty Companies. Company name, industry, employee count, annual revenue, and website URL map directly. Inmovilla parent-child company hierarchies translate to the Twenty Companies ParentId field. Multi-contact companies in Inmovilla collapse to a single Company record with multiple linked People records in Twenty.

Inmovilla properties do not have a direct Twenty equivalent — they become Opportunities with custom fields for property-type, price, surface area in m², number of bedrooms/bathrooms, energy certificate rating, and garage flag. Each property linked to its owner Contact and the agency Company record. Photos attached to properties re-upload to Twenty's file storage and linked to the Opportunity.

Inmovilla deal records map to Twenty Opportunities. Deal name, amount, stage, expected close date, and owner map directly. Deal stage values are mapped value-by-value to Twenty Opportunity Stage pick-list values. Stage-entered timestamps preserved as custom datetime fields on each Opportunity record.

Inmovilla deal stage names (e.g., 'Primera Visita', 'Negociación', 'Cerrada Ganada') are mapped to Twenty Opportunity Stage pick-list values. Custom stages require value-mapping setup in Twenty's Settings → Data Model before the migration runs. Stage probability is re-applied from source or set to Twenty defaults.

Inmovilla notes attached to contacts, companies, or properties migrate as Twenty Notes linked to the corresponding People, Companies, or Opportunity record. Original timestamps and note author preserved. Rich-text formatting in Inmovilla notes is flattened to plain text in Twenty Notes.

Inmovilla task records (call logs, email logs, meeting records) map to Twenty Tasks. Task subject, due date, completion status, and owner map directly. Task type (call, email, meeting) preserved as a custom select field on the Task record since Twenty Tasks do not natively distinguish activity type.

Inmovilla file attachments on properties and contacts are downloaded and re-uploaded to Twenty's file storage, then linked to the corresponding Opportunity (for property attachments) or People record (for contact attachments). File size limits apply — Twenty's upload handles files up to the storage configuration limit.

Inmovilla owner IDs are resolved by email match against Twenty Workspace Members. Agencies must invite all team members to Twenty before migration so the email lookup succeeds. Inmovilla agents without matching Twenty accounts are assigned to a fallback owner and flagged for manual reconciliation.

Inmovilla custom fields on properties (energy certificate rating, property type, orientation, floor number, elevator flag) have no native Twenty equivalent. We create corresponding custom fields on the Opportunity object in Twenty's Settings → Data Model before importing, then map values during the data load.

Inmovilla automated email sequences, lead-distribution rules, and task triggers are platform-native constructs with no Twenty equivalent. These must be rebuilt manually in Twenty's workflow builder (available on Organization tier) or via third-party automation tools. FlitStack exports workflow definitions as a rebuild reference document.

Inmovilla's client-facing property portal with virtual tour links and biometric signature integration does not translate to Twenty. The portal configuration must be replaced with a custom-built front-end connected to Twenty's API, or an alternative portal tool. This falls outside FlitStack's data-migration scope.