Migrate from Goals.com to Microsoft Dynamics 365 Sales

Goals.com Leads map directly to Dynamics 365 Sales Lead. The Goals.com lead generation pipeline stages (Inquiry, Filter, Grade, Distribute, Qualify) map to Dynamics Lead Status values. We preserve any Goals.com lead score, source attribution, and owner assignment in custom fields on the Dynamics Lead record during migration. Owner lookups are resolved via email-matched User records in the destination org.

Goals.com Deals map to Dynamics 365 Sales Opportunity. The Goals.com dealstage property maps to the corresponding Dynamics Sales Process stage name. Deal value, close date, and owner assignment migrate directly. Custom deal fields in Goals.com require pre-creation of custom Opportunity fields in Dynamics before migration; we document this gap in the pre-migration schema checklist.

Goals.com Sales Goals are a core native object (call volume targets, email targets, revenue targets). Dynamics 365 Sales has no native Goals or Targets object. We migrate goal definitions as custom numeric fields on the User object (individual rep targets) and/or as custom fields on the Opportunity object (pipeline revenue targets). Progress percentages are recalculated post-import in Dynamics using the migrated baseline values. The customer documents target-setting procedures for post-migration admin rebuild.

Goals.com Pipeline Stages map cleanly to Dynamics 365 Sales Process Stage values. Each Goals.com pipeline becomes a Dynamics Sales Process with corresponding Stage values. We preserve stage order, probability percentages (where set), and stage duration targets from Goals.com. Custom stage labels require explicit field mapping during migration scoping; we flag any non-standard stage names that need pre-creation in Dynamics before import.

Goals.com User accounts with role assignments (manager vs rep) map to Dynamics 365 Sales User records. Owner lookups on Leads, Opportunities, and Activities are preserved via ID mapping tables built during extraction. The migration resolves Goals.com owner_id to Dynamics User (by email match) and updates all relationship fields to point to the correct User record. Inactive Goals.com users require admin decision on whether to provision as inactive Users in Dynamics.

Goals.com Teams migrate as Dynamics Teams. Team membership links migrate as Team Membership records. Goals.com rep-to-manager hierarchy maps to Dynamics ManagerId on the User object, preserving the reporting structure that powers performance dashboards. If the customer's Teams use territory logic in Goals.com, we flag territory mapping as a post-migration configuration step.

Goals.com Notes, reminders, and customer interaction logs migrate as Dynamics Notes (if text-heavy) or Tasks (if action-oriented). We export activity records in bulk and load via Dynamics Bulk API with parent-record lookup resolution (ContactId, AccountId, OpportunityId). Goals.com does not store a full audit trail of every system event; historical activity depth is limited to what Goals.com exports, and we document this boundary during scoping. Large binary attachments migrate as Notes with file content where supported by the Dynamics API.

Goals.com commission records migrate as a custom Commission entity in Dynamics 365 Sales. Commission amounts, calculation basis, and rep attribution transfer as custom fields. Goals.com's commission calculation logic (active scoring rules and payout thresholds) cannot migrate as live configurations; we provide a commission schema template documenting the source logic for the customer's admin to rebuild using Dynamics 365 custom fields, workflows, or a dedicated commission app from AppExchange.