Migrate from Lifeline Suite to Twenty CRM

Lifeline Suite constituents (individuals with a relationship to the organization) map directly to Twenty People. All standard contact fields — name, email, phone, address — migrate with original create and update timestamps preserved as custom datetime fields for audit continuity.

Lifeline Suite constituents flagged as healthcare providers (NPI present, specialty populated) are identified during migration and routed to Twenty People with a custom Healthcare_Provider__c checkbox set to true. This allows Twenty users to filter the People list by provider status without querying custom fields separately.

Lifeline Suite organizations map to Twenty Companies. Company name, address, website, and industry fields migrate directly. Parent-child organization hierarchies in Lifeline translate to Twenty's companyId self-referential lookup where a parent company record exists. We preserve the original Lifeline organization ID as Source_System_ID__c on the Companies record for traceability and future delta synchronization. Industry values that have no direct Twenty equivalent are mapped to the closest available pick-list value.

Lifeline Suite links each constituent to one primary organization. The primary link becomes the People.companyId lookup in Twenty. Secondary organization relationships are preserved as a custom relation field or handled as additional People records if the constituent has multiple distinct roles.

Each Lifeline Suite gift record becomes a Twenty Opportunity. Gift amount maps to Opportunity.amount, gift date maps to Opportunity.closeDate, and gift status (completed, pledged, in-kind) maps to Opportunity stage values. The constituent who made the gift links as a personId on the Opportunity.

Lifeline Suite tracks which appeal or campaign generated each gift. We create a custom select field (Gift_Appeal__c) on Twenty Opportunities with the distinct appeal values from Lifeline as options. Appeal codes without a matching Opportunity are preserved in a reference lookup.

Lifeline Suite calculates lifetime giving totals per constituent. We create Lifetime_Giving__c (currency) and Last_Gift_Date__c (date) on Twenty People, populating them from a pre-aggregation of gift records before migration so the totals are immediately available in Twenty's People views. This pre-aggregation ensures accurate giving history without requiring retroactive calculations after import. The constituent's original Lifeline ID is stored as Source_System_ID__c for traceability. If Lifeline tracks multi-year giving streaks or recurring donor flags, those values are added as additional custom fields on the People record.

Lifeline Suite assigns giving levels (e.g., Friend, Donor, Patron, Major Donor). We create a Giving_Level__c pick-list on People with Lifeline's values as options and map each constituent's giving level directly. Level thresholds must be reconfigured in Twenty after migration based on your organization's criteria.

Lifeline Suite correspondence notes migrate as Twenty Notes attached to the relevant People record. Original note dates and the constituent name who authored the note are preserved in the Note record. Rich-text formatting in Lifeline notes is converted to plain text to match Twenty's Note format.

Lifeline Suite stores National Provider Identifier, specialty, and medical record number as native constituent fields. Twenty has no native equivalent for these. We create NPI__c (text), Specialty__c (select), and Medical_Record_Number__c (text) on People — these fields are searchable and filterable in Twenty but do not drive any native CRM behavior.

Lifeline Suite tracks how each constituent was referred (physician referral, self-referral, hospital transfer, community referral). We create a Referral_Source__c custom select field on People with the distinct referral values from Lifeline as options, preserving the source context for each constituent. We also add Referral_Date__c (date) to capture when the referral was made if that data exists in Lifeline. For complex referral relationships (multiple referring entities per constituent), we create a separate Referral__c custom object with a lookup to People rather than a flat select field. The original Lifeline referral record ID is preserved as Source_System_ID__c for future delta synchronization.

Gifts in Lifeline Suite are often designated to specific funds or programs (e.g., Capital Campaign, General Fund). We create a Gift_Designation__c select field on Opportunity with the distinct fund codes from Lifeline as options, preserving the allocation logic without requiring a separate custom object.

Lifeline Suite maintains code tables for constituent types, relationship types, and appeal categories. These are reference data — not transaction records. We import them as a static custom object in Twenty (Codes__c) so your team can reference the same lookup values that existed in Lifeline. The codes object has no link to other records and serves as a reference sheet.

Lifeline Suite stores document attachments (gift acknowledgments, pledge letters, constituent photos). Twenty's file import supports CSV-based file uploads. We re-upload attachments to Twenty Files and attach them to the relevant People or Opportunity record. File size limits per Twenty's upload constraints apply.