Migrate from folk to Microsoft Dynamics 365 Sales

folk Contacts of person subtype map to either Dynamics 365 Lead (for unqualified or early-stage records) or Contact (for qualified records linked to an Account). We establish the split rule during scoping using the contact's last activity date, tag set, and any group membership signals to determine qualification status. The original folk contact record is preserved in a custom field original_folk_id__c on both Lead and Contact for reconciliation.

folk Contacts of company subtype map directly to Dynamics 365 Account. The folk company contact's name becomes Account Name, website domain maps to Website, and any associated address fields map to the Address composite. Company-type contacts that have person-type contacts linked to them inherit those person contacts as Dynamics 365 Contacts under the Account via a lookup relationship we resolve at migration time.

folk Groups are organizational containers that serve two distinct functions: company-oriented Groups (e.g., Clients, Prospects) map to Dynamics 365 Account records with the Group name as Account Name; segment-oriented Groups (e.g., VIP Contacts, Event Attendees) map to Dynamics 365 Contact List (a standard entity accessible via the marketing area). We classify each Group during discovery and map accordingly. Group membership for segment-type Groups is preserved as ContactListMember records.

folk defines custom fields per-Group, meaning the same contact record can have different field schemas depending on which Group it belongs to. We enumerate every distinct field schema across all Groups during discovery and pre-create the union of all custom fields as global custom fields on the Dynamics 365 Lead and Contact entities. Where contacts belong to multiple Groups with conflicting field values, we apply a priority rule (most recently modified value wins) and document the conflict for the customer's review.

folk Notes attached to Contacts migrate to Dynamics 365 Annotation records linked to the corresponding Lead, Contact, or Account via the objectid and objecttypecode fields. Note body, author attribution, and creation timestamp transfer directly. Notes on company-type contacts migrate as Annotations on the Account record.

folk tags are a flat string array per contact with no hierarchy. We migrate tags as a comma-separated string in a custom text field on Lead and Contact. For customers who use tags as a primary segmentation signal, we recommend migrating tags to Dynamics 365 Marketing Tags (accessible in the marketing module) or to a custom multi-select picklist if the tag set is bounded and known.

folk Reminders carry a due date, assignee (owner), and text description. We migrate Reminders to Dynamics 365 Task records with Subject (from reminder text), DueDate (from reminder due date), and Status set to Not Started. Owner mapping requires resolving the folk owner email to a Dynamics 365 User record; any unresolved owners are held in a reconciliation queue for the customer's admin to provision.

folk Groups that contain deal-oriented pipeline data (stages, amounts, close dates) map to Dynamics 365 Opportunity records. The folk pipeline view stage names map to Dynamics 365 Opportunity Stage values within a Sales Process that we create during schema setup. For Groups without deal data, pipeline views are documented as reference data and do not generate Dynamics 365 Opportunity records.

folk's activity timeline captures emails, meetings, and calls per contact. We extract activity data from the CSV export where present and map to Dynamics 365 ActivityPointer records with the appropriate Activity typecode. Activity timestamps preserve the original folk timestamps for timeline ordering. Note that CSV export may not capture the full rich-text body or attachment references from folk's activity timeline; we flag any gaps during the discovery audit.

folk attachments exported as file URLs or downloaded files migrate to Dynamics 365 Annotation note attachments linked to the parent record. If the customer uses Dynamics 365's SharePoint integration, we can route attachments to SharePoint document libraries and link them via the SharePoint document location entity. File size limits follow the Dynamics 365 attachment limit (32 MB per file for notes).