Migrate from Perfect Portal to Twenty CRM

Perfect Portal client records map directly to Twenty Companies with a straightforward field mapping. The client name becomes Company.name, and any client-level address data maps to the corresponding address fields in Twenty. If Perfect Portal stores a client website URL, that populates the Company.domain field. This mapping preserves all client-level information in a format Twenty recognizes.

Perfect Portal matters become Twenty Opportunities linked to the Company record representing the client. The matter name maps to Opportunity.name, and the matter amount or value maps to Opportunity.amount for financial tracking. Matter stage values require value-mapping to Twenty's stageName pick-list, with each Perfect Portal stage mapped to the appropriate Twenty opportunity stage.

Each Perfect Portal matter stage such as Intake, Under Review, and Closing maps to a corresponding Twenty Opportunity StageName value through a value-mapping configuration. Probability percentages and forecast category settings re-applied based on Twenty's stage model for accurate pipeline reporting. Stage-entered timestamps preserve as custom datetime fields on the Opportunity record for historical tracking.

Perfect Portal contacts map to Twenty People records with standard fields including name, email, phone, and job title. The contact's linked client becomes the People.companyId foreign key referencing the mapped Company record, establishing the relationship between contacts and their organization. This linking maintains the connection between individuals and their company in Twenty's relational model.

Perfect Portal activity entries including calls, emails, and notes migrate as Twenty Notes attached to the relevant People or Company record. Original timestamps and author information preserve during migration for complete audit trails. Rich-text formatting handles where supported, though some formatting may simplify during transfer to maintain compatibility.

Perfect Portal tasks with due dates and assignees map directly to Twenty Tasks, preserving task status, priority, and linked record references. Unassigned tasks land with the migrated owner if available, or a fallback assignee designated during migration setup for proper task management continuity.

Attachments stored in Perfect Portal are downloaded and re-uploaded to Twenty's file storage, maintaining file names and upload dates. File size limits apply per Twenty's storage configuration, which your admin should verify can accommodate your largest files. Inline images embedded in notes are extracted and rehosted as separate files to ensure they display correctly in Twenty.

Perfect Portal custom fields on matters require corresponding Twenty custom fields on the Opportunity object before migration. Field types map directly: text to text, number to number, date to date, pick-list to select. Multi-select values in Perfect Portal map to Twenty multi-select fields, preserving all custom data captured on matter records.

Perfect Portal custom properties on contacts create custom fields on Twenty People records during migration. Any billing flags, source tracking data, or custom identifiers preserve as text or select fields depending on the original value type. This ensures all contact-specific custom data transfers to Twenty for complete records.

Perfect Portal users match to Twenty Workspace Members by email address for proper ownership attribution. Unmatched owners flagged before migration for your team to resolve by inviting them to Twenty or assigning their records to a fallback WorkspaceMember. Records from unmatched owners land without an assignee for manual resolution after migration completes.

Perfect Portal third-party access records for real estate agents, referral partners, and other external parties split into People records with a linked Company representing their organization. Their Perfect Portal access permissions and matter-level transparency settings cannot migrate to Twenty's workspace-wide permission model. Twenty permissions rebuild separately by workspace admin post-migration to replicate the access control functionality.