Migrate from Goals.com to Pipedrive

Goals.com Lead records (including generation source, grade, and qualification status) map to Pipedrive Lead (from Leads Beta or Pipedrive's Person object depending on the customer's enabled features). We preserve the original Goals.com lead_id as a custom field for reconciliation. The qualification status property from Goals.com becomes a custom picklist field on the Pipedrive record.

Goals.com Deals map 1:1 to Pipedrive Deals. Deal value, stage, owner, expected close date, and notes transfer directly. Pipeline stages in Goals.com become Pipedrive Pipeline stages — we pre-create the pipeline in Pipedrive with matching stage names and probability percentages before import so that stage mapping is a direct field-to-field transfer rather than a post-import cleanup step.

Goals.com Sales Goals (call volume, email count, revenue targets) have no native Pipedrive equivalent because Pipedrive's goal tracking is a paid add-on ($15/user/mo) separate from core CRM. We convert Goals.com goal definitions to custom numeric fields (e.g., target_calls__c, target_emails__c, target_revenue__c) on the Deal or Organization object and set baseline values from the most recent goal period. Goal progress percentages are recalculated in Pipedrive after import based on linked activity and deal data.

Goals.com pipeline stages map to Pipedrive Pipeline stages. We create the Pipedrive pipeline before any Deal import, set stage order, assign probability percentages (matching Goals.com where defined), and configure stage-level visibility settings. If Goals.com uses a naming convention to simulate hierarchy (e.g., Company > Department > Rep goals), we flag these for manual restructuring as separate Pipedrive pipelines or custom fields post-import.

Goals.com commission records migrate as data rows. We create a custom DealsCommission object in Pipedrive (using custom fields: commission_amount__c, payout_status__c, deal_id__c lookup, rep_name__c) or attach commission data as custom fields on the linked Deal record. Commission payout rules and active scoring logic are not transferable as rules — these require manual rebuild using Pipedrive's custom fields and formula fields post-migration.

Goals.com user accounts with role assignments (manager vs rep) map to Pipedrive Users. We match by email address and map the Goals.com role to Pipedrive's permission sets or admin flag. Team memberships migrate as Pipedrive Groups, with each Goals.com team becoming a Pipedrive group that managers and reps are assigned to for reporting visibility.

Goals.com activity records (notes, reminders, call logs, meeting records) map to Pipedrive Activities. Each activity type becomes a Pipedrive Activity type (call, task, meeting, note). We set ActivityDate from the original Goals.com timestamp, link the Activity to the resolved Person or Deal via Pipedrive's deal_id and person_id foreign keys, and assign the OwnerId by email-matching to the migrated User record.

Goals.com teams migrate as Pipedrive Groups. Group membership is preserved by linking each migrated User to the corresponding Pipedrive Group. Pipedrive's Group-based reporting allows managers to view team performance dashboards matching the Goals.com team contest and visibility model.

Goals.com historical contest results and leaderboard data export as rows with contest_name, participant_rep, score, rank, and period. We map these to custom fields on the relevant Deal or Organization records, or create a ContestResults custom object with these fields. Active contest scoring rules and leaderboard logic do not migrate as rules — we provide a contest schema template documenting the original Goals.com rule structure for manual rebuild in Pipedrive.

Goals.com file attachments linked to Deals or Persons migrate to Pipedrive's attachment model. We export the file content, resolve the parent record reference, and upload via Pipedrive's Files API or attach directly to the Deal or Person record. Large binary attachments may require a separate file transfer step with a manifest of the source file paths for customer verification.