Migrate from Notifi to Twenty CRM

Notifi contacts map to Twenty's People object. Each Notifi contact carries name, email, phone, and job title — all direct field equivalents in Twenty's People schema. The contact's primary company link in Notifi resolves to a People.companyId relation in Twenty after the Companies object migrates first.

Notifi companies map to Twenty's Companies object. Company name, domain, industry, employee count, and annual revenue map directly. Notifi's parent-company hierarchy (if used) resolves to Companies.parentId in Twenty, requiring parent records to migrate before child records to satisfy foreign-key constraints.

Notifi jobs and deals map to Twenty Opportunities. The opportunity name, amount, stage, and expected close date carry over directly. Notifi's job status (Scheduled, In Progress, Completed, Invoiced) maps to Twenty's Opportunity stage values with a value-mapping configuration applied during migration.

Notifi estimates have no direct Twenty equivalent. We create an Estimate Custom Object in Twenty containing estimate number, line items, total amount, status, and linked Opportunity. Line items migrate as a JSON-serialized array in a custom field unless Twenty's schema is extended with a dedicated line-item relation object.

Notifi invoices map to a custom Invoice object in Twenty. Invoice number, issue date, due date, total, payment status, and linked Opportunity preserve the financial record. Payment transactions attached to Notifi invoices migrate as Payment records linked to the Invoice object. QuickBooks sync data is not transferable and must be reconciled in QuickBooks directly.

Notifi call logs migrate as Twenty Tasks with Task.type set to 'Call'. Subject carries the contact name and call direction. Task.status reflects call completion. Duration, disposition notes, and recording links (if available) store in custom Task fields. Original call timestamps preserve as Task due dates for audit continuity.

Notifi text conversations migrate as Tasks with Task.type set to 'SMS'. The message body stores in Task.body. Linked People and Opportunities preserve context. Thread history is flattened into individual Task records ordered by timestamp to maintain conversation sequence without native threading in Twenty.

Notifi email activities (sent and received) migrate as Tasks with Task.type set to 'Email'. Subject and body map to Task subject and body fields. Email status (opened, replied) stores in a custom field. Thread associations preserve by linking related Tasks to the same People record.

Notifi notes attached to contacts, companies, or jobs migrate to Twenty Notes. Note body preserves rich-text formatting where Notifi stores it. File attachments (photos, documents) re-upload to Twenty's file storage and link back to the related People, Company, or Opportunity record.

Notifi custom properties (certification types, service categories, scheduling preferences) map to Twenty Custom Fields. We create fields with matching types — text, number, select, multi-select — on the appropriate Twenty object. Multi-select values in Notifi serialize as comma-separated strings in Twenty's text-based multi-select until native array support is confirmed in Twenty's field schema.

Notifi custom properties that reference other records (e.g., a service-area linked to a territory object) map to Twenty Custom Objects with relational fields. We first migrate the referenced object, then link the Custom Object records via the relation key extracted from Notifi's API response.

Notifi owner IDs resolve by email match against Twenty workspace members. Unmatched owners are flagged before migration — teams either invite the user to Twenty first or assign records to a fallback workspace member. Owner resolution is required before any record with an owner field can commit.

Notifi workflows, automations, and sequences do not migrate. These represent process logic that must be rebuilt in Twenty's workflow builder or via external automation tools. FlitStack exports your Notifi workflow definitions (trigger conditions, action steps, timing rules) as a structured JSON document for your admin to reference during rebuild.

Notifi reports and dashboards do not transfer. The underlying data migrates, so reportable fields are available in Twenty, but report configurations and saved views must be rebuilt. We provide a data dictionary mapping Notifi report field names to their Twenty equivalents to accelerate the rebuild.