Migrate from Goals.com to HighLevel

Goals.com Leads map to GoHighLevel Contacts. The lead's name, email, phone, company, source, status, and grading properties map to the corresponding GoHighLevel Contact fields. Owner lookup resolves via email match to the GoHighLevel User. Goals.com lead scoring grades migrate as a custom Contact field numeric value. Any Goals.com lead assignments to team territories map to GoHighLevel tags or a custom location field depending on the customer's segmentation strategy.

Goals.com Deal records map to GoHighLevel Opportunities. Deal name, value, stage, owner, expected close date, and company association map to the GoHighLevel Opportunity fields. Goals.com deal stages map to GoHighLevel pipeline stages; each Goals.com pipeline becomes a separate GoHighLevel pipeline. Deal owner resolves to the GoHighLevel User by email. Historical deal value and stage timestamps preserve for reporting continuity.

Goals.com pipeline stages map 1:1 to GoHighLevel pipeline stages within the corresponding pipeline. Stage names, order, and probability values transfer. We configure the GoHighLevel pipeline structure before any Deal records import so that the stage lookup is satisfied at import time. Goals.com's flat pipeline model (single pipeline per account) maps cleanly to GoHighLevel's single default pipeline; multi-pipeline setups require a separate GoHighLevel pipeline per Goals.com pipeline.

Goals.com Sales Goals (call targets, email targets, revenue targets) have no native GoHighLevel equivalent. We create a custom object called Sales_Goals in GoHighLevel with fields for target type, target value, period, and owner. Historical goal completion percentages are stored as custom fields on the custom object. Active goal definitions are recreated as new custom object records during migration. Ongoing goal progress tracking requires manual configuration in GoHighLevel using Opportunities, pipeline stages, or a third-party reporting integration post-migration.

Goals.com commission records migrate as a custom object in GoHighLevel called Commission_Records with fields for rep, deal reference, commission amount, payout status, and period. Goals.com's active commission calculation rules (percentage splits, tiered payout logic, territory bonuses) cannot be exported as code — they are stored as application logic, not data records. We deliver a Commission_Schema_Template documenting the customer's active rules, field mappings, and tier logic so that the customer's admin can rebuild the payout engine in GoHighLevel using a custom object, workflows, or a dedicated commission app.

Goals.com user accounts with role assignments (manager, rep, admin) migrate as GoHighLevel User records. Manager-rep hierarchy resolves via the owner lookup chain in Goals.com, which maps to GoHighLevel's user reporting structure. Active status and last-login timestamps transfer. Users without a matching email in the destination GoHighLevel account go to a provisioning queue for the admin to create before import.

Goals.com notes and reminders attached to Leads or Deals migrate as GoHighLevel Notes linked to the corresponding Contact or Opportunity. Note timestamps preserve for activity timeline ordering. Goals.com does not store a complete audit trail of all system events — only explicitly logged notes transfer. Email and call logs stored as activity records in Goals.com migrate as GoHighLevel Tasks with the appropriate task type.

Goals.com historical contest results and leaderboard data migrate as a custom object called Contest_History in GoHighLevel with fields for contest name, period, participant, score, and rank. Active contest configurations (scoring rules, point allocations, leaderboard logic) are stored as application logic, not data records, and cannot be exported. We deliver a Contest_Rules_Inventory documenting the customer's active contest parameters for manual rebuild in GoHighLevel using custom objects, tags, and reporting filters.