Migrate from APRO CRM to Twenty CRM

APRO contact records map to Twenty People objects. The name, email, phone, job title, and address fields transfer directly. APRO contacts without a company association land in Twenty as standalone People records. Owner assignment resolves via email match against Twenty workspace members.

APRO company records map to Twenty Companies objects. Company name, domain/website, industry, employee count, and revenue fields map to Twenty's name, domain, industry, employees, and revenue fields. Parent-child company hierarchies in APRO use a parentId lookup that translates directly to Twenty's parentCompanyId.

APRO deals (property listings and sales) map to Twenty Opportunities. The deal name becomes the opportunity name, amount maps to the expected revenue field, close date maps to the close date field, and stage maps to a custom stage field. APRO pipeline stage values require value-by-value mapping to Twenty opportunity stages, which must be pre-created in Twenty's Settings → Data Model before import.

APRO's property-specific listing records — with fields like listing status, property type, address, MLS number, and automatch criteria — require a custom object in Twenty. FlitStack creates a 'Property' custom object with matching fields and preserves the APRO property ID as a source_system_id custom field for traceability and delta-run de-duplication.

APRO automatching links contacts to property listings based on criteria (location preference, price range, property type). This N:1 or N:N association translates to a custom junction object in Twenty — either a 'PropertyInterest' object linking People to Property records, or a multi-select custom field on the People object, depending on how the automatch data is structured in APRO.

APRO call logs, emails, meetings, and notes map to Twenty Tasks (for call and email activities with type classification) and Notes objects (for free-form notes). Original timestamps, activity type, and body content transfer. The parent record link (contact or company) maps to Twenty's linkedId and linkedRecordId fields.

APRO's bundled IP telephony produces call records with duration, disposition, recording URL, and caller ID. Twenty has no native telephony integration — call activity migrates as Tasks with Type='Call', but recording URLs and telephony disposition codes are preserved as custom fields for reference. Rebuilt telephony integrations (via a third-party tool) will need to re-link to migrated call records.

APRO owner IDs (agents, brokers) resolve against Twenty workspace members by email match. Unmatched owners are flagged before migration. APRO user role assignments (lead agent, showing coordinator, transaction manager) translate to Twenty role configurations in Settings → Roles — the source role name is preserved in a custom field for admin reference.

APRO's built-in website integration captures visitor statistics (page views, form submissions, live chat sessions) linked to contacts. Twenty has no native website visitor tracking — these statistics are exported as a CSV reference file and linked to the migrated People records as custom fields. The data serves as historical context rather than live tracking.

APRO custom automation algorithms (automatch rules, follow-up triggers, listing-update workflows) do not transfer. FlitStack exports workflow definitions and rule logic as a structured document that your Twenty admin uses to rebuild automations in Twenty's workflow builder. Note: Twenty's workflow builder supports event triggers but lacks native sequencing — consider third-party tools for complex follow-up cadences.