Migrate from Goals.com to Salesforce Sales Cloud

Goals.com Leads map to Salesforce Lead as a direct 1:1 transfer. Goals.com lead generation, inquiry capture, filtering, grading, distribution, and qualification stages transfer as text values into a custom picklist field goals_lead_stage__c since Goals.com stage labels do not map to Salesforce standard Lead Status values. The customer's admin defines the Salesforce Lead Status mapping during scoping. Any lead scores from Goals.com's grading step migrate to a custom number field goals_lead_score__c.

Goals.com Deals map to Salesforce Opportunity. The Deal name, value, stage, owner assignment, and created date transfer directly. Goals.com's flat Deal structure means there is no Account or Contact parent relationship in Goals.com; we create the parent Account from the Deal's associated company name before Opportunity import, and link the Opportunity to a Contact resolved from Goals.com's lead or contact records. Stage names map to Salesforce StageName values, and the Goals.com pipeline assignment maps to a Salesforce Record Type.

Goals.com pipeline stages map to Salesforce Opportunity Stages. Each Goals.com stage gets a corresponding Salesforce StageName entry with probability values set to match Goals.com's stage weights. Stage sequence order is preserved. If Goals.com uses custom stage labels (Prospecting, Qualification, Proposal, Negotiation, Closed Won, Closed Lost), we configure Salesforce Sales Processes to match the exact sequence and labeling.

Goals.com Sales Goals have no direct Salesforce equivalent because Salesforce does not include a native goal-setting object. We pre-create a custom object goals_sales_goal__c with fields for goal type (call volume, email volume, revenue target), target value, start date, end date, owner reference, and linked opportunity or account. Goal progress percentages are recalculated post-import in Salesforce using a custom progress formula field or a Salesforce Flow that recomputes against actual Opportunity values. The customer chooses whether to display goals via a custom Lightning component or via Salesforce Revenue Intelligence if that add-on is licensed.

Goals.com commission records migrate to a custom object goals_commission__c linked to the Opportunity or User. Fields include commission amount, calculation basis, payout status, and payee reference. Goals.com's active commission calculation rules (percentages, tiers, accelerators) are not migratable because they are stored as platform logic rather than data records. We export the commission data (historical payouts, rep assignments, deal references) and deliver a written commission rule schema template that the customer's admin rebuilds in Salesforce using custom fields, Flow, or Salesforce Revenue Cloud.

Goals.com user accounts migrate to Salesforce User records resolved by email address match. Goals.com role assignments (manager vs rep) map to Salesforce Role in the role hierarchy or to a custom field goals_role_type__c if the Salesforce role hierarchy is not yet configured. Inactive Goals.com users migrate as inactive Salesforce Users to preserve historical owner assignments. Any Goals.com user without a corresponding Salesforce license goes to the reconciliation queue for the customer's admin to provision before record import resumes.

Goals.com team structures map to Salesforce Public Groups. We extract Goals.com team memberships and build Public Group membership during migration. If the customer needs team-level reporting beyond Public Group visibility (a custom team object for territory or division alignment), we create a goals_team__c custom object with team membership records linked to the User object. The customer chooses the team reporting model during scoping.

Goals.com notes, reminders, and customer interaction records map to Salesforce Task or Event depending on the record type. Notes migrate as Salesforce Note records linked via ContentDocumentLink to the parent Lead, Contact, Account, or Opportunity. Reminders and follow-up tasks migrate as Task records with Status, Priority, and ActivityDate preserved. Goals.com does not store a full audit trail of every system event; we migrate what is accessible through the export and flag any gaps in the historical timeline.

Goals.com active contest configurations, scoring rules, point allocations, and leaderboard logic are stored as platform rules rather than data records and do not migrate. We export historical contest results and performance data as records in a goals_contest_history__c custom object. We deliver a written contest schema template specifying the structure the customer's admin needs to rebuild in Salesforce (using a custom object, custom fields, and a leaderboard Lightning component or report). Active contest rules require manual rebuild post-migration.

Goals.com file attachments linked to Deals, Leads, or activities migrate as Salesforce ContentDocument records attached via ContentDocumentLink to the corresponding Lead, Contact, Account, or Opportunity. File names and any associated metadata transfer. Large binary attachments may require a separate file transfer step outside the standard API batch if size limits are encountered.

Goals.com Deals carry an associated company name that we promote to a Salesforce Account record before Opportunity import. The company name becomes the Account Name; any domain or address data from Goals.com maps to Account Website and Address fields. Account is created first so that the Opportunity AccountId reference is satisfied at import time. Dedupe is performed on Account Name.

Goals.com Lead or Contact records associated with a Deal resolve to Salesforce Contact after Account creation. The Contact's email, phone, title, and address fields map 1:1. Contact is created after Account so that AccountId is available for the Contact record. If Goals.com does not store a separate Contact record and only has Deal-level contact information, we create the Contact from the Deal contact details and attach it to the Account.