Migrate from Soffront to Microsoft Dynamics 365 Sales

Soffront Contacts map directly to Microsoft Dynamics 365 Sales Contact. Standard fields (full name, email, phone, address) use standard Dataverse attribute names (fullname, emailaddress1, telephone1, address1_*). Group assignments from Soffront map to Team membership or security roles in Dynamics 365. Soffront lifecycle stage values are preserved in a custom field soffront_lifecycle_stage__c on Contact for reporting continuity.

Soffront Account records map to Microsoft Dynamics 365 Sales Account. The Account-Contact relationship is preserved by creating Accounts first and resolving the parent Account lookup before Contact import. Industry, size, and custom properties map to standard or custom fields on Account. Account names serve as the dedupe key during import to prevent duplicate Accounts.

Soffront Deals map to Microsoft Dynamics 365 Sales Opportunity. The deal stage names from Soffront map to Dynamics 365 Opportunity StageName values; we perform a value-mapping exercise during discovery because stage names vary between Soffront instances. Deal amount maps to Amount, owner maps to OwnerId via email match against the Dynamics 365 User table. If the deal has a parent Account in Soffront, we set AccountId on the Opportunity during import.

Soffront Activities with type labels (call, email, meeting, task) map to Dynamics 365 Dataverse Task, Event, or EmailMessage records. Calls map to Task with TaskSubtype=Call and call duration in a custom field. Emails map to EmailMessage records (body content) linked to an Activity Task for timeline display. Meetings map to Event with StartTime and EndTime preserved. Activity type labels and custom activity fields require field-level mapping during discovery. Soffront API pagination at 500 records per call means we chunk activity extraction by date range or owner to ensure complete coverage.

Soffront Projects include status, milestones, managers, resources, and due dates. If the destination Microsoft Dynamics 365 Sales org has Project Operations licensed, we map to the Project entity. If not, we map to a custom project entity created in the destination. Project tasks migrate as related records with parent-project lookups resolved at import time. Milestone dates map to custom date fields or the Project timeline fields depending on destination schema.

Soffront support Tickets map to Microsoft Dynamics 365 Sales Case if Service Cloud is included in the destination. Ticket status, priority, assignee, and conversation history migrate. Conversation threads migrate as EmailMessage records linked to the Case. If the destination does not include Service Cloud, we map Tickets to a custom Case entity on the Sales entity set. Ticket type labels map to Case Origin or a custom field depending on the destination's case configuration.

Soffront Knowledge Base articles export with their category assignments. We recreate the category hierarchy in Dynamics 365 Knowledge Management before importing articles so that article-category relationships are preserved. If Dynamics 365 uses a flat KB structure, we create categories that mirror Soffront's taxonomy and map articles accordingly. Article content migrates as knowledgearticle records with the kbmemArticleContent field containing body text. Status (published, draft) migrates to the article's statecode.

Soffront custom objects migrate to Dataverse custom entities with __c suffix API names. We pre-create the destination schema during discovery including all custom attributes, lookup relationships to standard entities (Account, Contact, Opportunity), and any validation rules. Custom field types from Soffront (text, number, picklist, date, checkbox) map to equivalent Dataverse attribute types. The schema is deployed to a Sandbox first for validation before production migration.

Soffront custom fields on Contacts, Accounts, Deals, and Activities vary between instances because of Soffront's customization-first design. We perform a field inventory during discovery that captures every custom field's name, data type, and picklist values. The inventory generates a mapping document pairing each Soffront custom field to a new or existing Dynamics 365 custom attribute before any data moves. Picklist values are migrated as Option Set values in Dataverse.

Soffront file attachments linked to Contacts, Deals, Tickets, and Projects export and re-upload to Dynamics 365. Annotations with file attachments become Note (annotation) records with documentbody populated. If the Dynamics 365 org uses SharePoint or Azure Blob for document storage, we configure the document location during migration. File size limits and storage location vary by Soffront edition and are documented during discovery.

Soffront Groups organize records for access control and segmentation. We map group memberships to Dynamics 365 Teams (or Azure Active Directory groups synced to Teams) and replicate the sharing model using Team membership. If Soffront groups have hierarchical nesting, we flatten the structure into Teams with appropriate parent-team assignments in Dynamics 365. Group-based record assignments migrate as OwnerId on the record.