Migrate from Goals.com to HubSpot

Goals.com contact records map directly to HubSpot contacts via email matching. Standard fields—email, phone, name, job title—migrate as HubSpot native properties without transformation. Goals.com contact IDs preserve as Source_System_ID__c custom properties for traceability and delta-run deduplication. Any duplicate contacts identified during migration flag for manual review before final import. Custom fields on Goals.com contacts create corresponding HubSpot custom properties, ensuring no data loss during the transition.

Goals.com company records map to HubSpot companies with direct field translations for name, domain, industry, employee count, and employee range as HubSpot native properties without transformation. Goals.com parent-child relationships preserve via HubSpot's parent company association field, maintaining organizational hierarchies post-migration. Any duplicate companies identified during import flag for manual review before finalization, ensuring data integrity across the company object.

Goals.com deals migrate to HubSpot deals with deal name, amount, stage, close date, and owner preserved. HubSpot's deal pipelines support multiple pipelines natively — Goals.com's single pipeline maps to a default HubSpot pipeline. Deal associations with contacts and companies maintain through contact and company IDs throughout migration. Custom fields on Goals.com deals create HubSpot custom properties for complete data preservation.

Goals.com's native Goals object has no HubSpot equivalent. We create a Goals__c custom object with Goal_Name__c (text), Target_Value__c (number), Current_Value__c (number), Start_Date__c, End_Date__c, and Status__c (picklist) custom fields. Each goal record links to a HubSpot contact or company owner via lookup field. Goal progress percentage calculates from current_value divided by target_value. Any Goals.com custom fields on goals migrate as additional custom properties on Goals__c, preserving the full data set.

Goals.com key results map to a Key_Results__c custom object linked to Goals__c via lookup field. Metric type, target value, and progress percentage migrate as custom fields on this object. Each key result includes a Name field for the result description, a Metric_Type__c picklist (number, percentage, currency), Target__c for the target value, and Progress__c for current percentage. Key results also track Start_Date__c and End_Date__c for time-bound metrics, preserving the full Goals.com key result structure within HubSpot's custom object framework.

Goals.com call logs (duration, outcome, notes, timestamp) map to HubSpot Call engagements via the Engagement API. Call direction, duration in seconds, and outcome notes preserved as engagement metadata. Call disposition maps to HubSpot call outcome picklist values for consistent reporting. If Goals.com recorded call recordings, these URLs store as engagement metadata for playback in HubSpot. Call associations with contacts maintain via email match, ensuring activity history links to the correct HubSpot contact record.

Goals.com email activity maps to HubSpot Email engagements. Subject, body text, timestamp, and recipient associations migrate. Attachments re-uploaded to HubSpot Files and linked to the engagement record. Email tracking status (opened, clicked, bounced) from Goals.com preserves as custom properties on the engagement. All email associations with contacts maintain via email match, preserving the full conversation history within HubSpot's engagement timeline.

Goals.com commission calculations migrate as Deal_Commission__c custom number fields on HubSpot deals. Percentage-based and flat-fee commission structures preserve as separate fields if both exist in Goals.com. Each deal with commission data creates Commission_Pct__c (percentage) and Commission_Amount__c (calculated dollar value) as custom properties. Commission eligibility criteria and tiered rate logic require manual recreation in HubSpot using workflow formulas or a dedicated commission tool post-migration.

Goals.com users resolve by email match against HubSpot owners. Unmatched users flagged before migration — team either creates HubSpot accounts or assigns records to a fallback owner to prevent orphaned records. Owner mapping preserves the original Goals.com user ID as Owner_ID__c for audit traceability. Inactive Goals.com users map to a deactivated HubSpot owner placeholder to maintain historical assignment records. Post-migration, HubSpot owner reports reflect the migrated assignments accurately.

Goals.com file attachments on contacts, companies, or deals re-upload to HubSpot Files. File metadata (name, size, upload date) preserved. Inline images in notes download and re-host in HubSpot's file storage. Attachment associations maintain via HubSpot's engagement API, linking files to the original contact, company, or deal record. File type validation ensures attachments display correctly post-migration.