Migrate from Function 365 to Twenty CRM

Function 365 Account maps directly to Twenty CRM Company. The Account.Name becomes Company.name (text). Account.website maps to Company.domainUrl. Account.industry maps to a Twenty Select-type Industry field if configured. Parent account hierarchies (Account.ParentAccountId) map to a self-referential Company relation in Twenty. Multi-address accounts (Address fields) are consolidated into Twenty's primary address fields.

Function 365 Contact maps to Twenty CRM People as a primary mapping. Contact.firstname → People.firstName, Contact.lastname → People.lastName, Contact.emailaddress1 → People.email, Contact.mobilephone → People.phone (or a custom phone field if multiple phone types exist). The Contact's parent CustomerId (Account lookup) maps to the People.company relation by email-domain matching or explicit Account.Name lookup.

Function 365 Lead and Contact both map into Twenty CRM People. The distinction is preserved via a People.type field (set to 'Lead' or 'Contact' during import) and a status flag. If your Function 365 has closed/won leads that represent existing customers, those records receive a 'Converted Lead' tag in Twenty so your sales team can filter them separately without losing history.

Function 365 Opportunity maps to Twenty CRM Opportunity with minimal transformation. Opportunity.name → Opportunity.name, Opportunity.estimatedvalue → Opportunity.amount (Currency type), Opportunity.closeprobability → Opportunity.probability (Number 0–100), Opportunity.estimatedclosedate → Opportunity.closeDate. The Dynamics StageCode (option set) maps to a Twenty Select-type Stage field value-by-value.

Function 365 Lead records that have been converted into Opportunities retain both the original LeadId and the new OpportunityId. We map the converted Opportunity to Twenty Opportunity directly. The original Lead fields (lead quality score, source campaign) are preserved as custom fields on the Twenty Opportunity record so closed-loop reporting remains intact.

Function 365 Task (activity) maps to Twenty CRM Task. Task.subject → Task.title, Task.scheduledend → Task.dueDate, Task.statuscode → Task.status, Task.ownerid → Task.assignee (resolved by email to a Twenty Workspace Member). Task regarding fields (RegardingObjectId pointing to Account, Contact, or Opportunity) map to the Task's relation field in Twenty.

Function 365 email activities are stored as EmailSendPointer records with body text in EmailRouterMailboxTrackingPolicy-linked tables. We extract the subject, body text, sender, recipients, and sent-on timestamp and represent each email as a Twenty Task with Type='Email', subject from the email subject line, and the original timestamp preserved. Email threading is not maintained as a native feature in Twenty but can be reconstructed from a related-email custom field.

Function 365 PhoneCall activity maps to Twenty Task with Type='Call'. Subject is built from the CallDirection (Incoming/Outgoing) and the regarding record name. Duration (PhoneCall.duration) is stored as a custom Number field (CallDurationMinutes__c) since Twenty's native Task does not include duration.

Function 365 Appointment maps to Twenty Task with Type='Meeting'. Subject, scheduledstart, scheduledend, and location are mapped to the corresponding Twenty Task fields. The Appointment's requiredattendees (PartyList of Contact/Lead records) are stored as a custom Multi-Select relation field on the Twenty Task since Twenty does not have native attendee tracking.

Function 365 Annotation (notes and file attachments) maps to Twenty CRM Notes attached to People, Companies, or Opportunities by the RegardingObjectId reference. The note text maps to Note.body; the createdon timestamp and notetext (if a string field) maps to a custom datetime field. File attachments are downloaded from Dynamics SharePoint/Note locations and re-uploaded to Twenty's file storage.

Function 365 custom entities (tables created via Power Apps maker or Xrm tooling) map to Twenty CRM Custom Objects. We create the matching Twenty custom object in Settings → Data Model before import, then map each custom entity attribute to the corresponding Twenty field. Custom entity relationships (many-to-many via intersect tables) map to Twenty relation fields.

Function 365's N:N contact-to-account relationship via Connection or the inverse CustomerAddress role is flattened into Twenty's People.company relation (a single relation per person). The most recently modified or primary company per contact is designated as the Twenty relation; any additional companies are stored in a custom Multi-Relation field.

Function 365 SalesOrder and Invoice entities have no direct Twenty CRM equivalent. We preserve them as a custom object (e.g., Orders) with fields for order number, amount, status, date, and related Opportunity. Order line items are stored as a custom relation sub-object. This gives you a reference record even though Twenty does not natively support order management.

Function 365 SystemUser records map to Twenty Workspace Members. Resolution is by email address: each SystemUser.internalemailaddress is matched to a Twenty user account. Unmatched SystemUser records are flagged before migration so your team can either invite them to Twenty first or assign their records to a fallback user. User business unit hierarchies do not translate to Twenty's flat permission model.