Migrate from RedEye to HubSpot

RedEye customer profiles map directly to HubSpot contacts. Every RedEye customer record becomes a HubSpot contact with standard properties (first name, last name, email, phone) pulled from the profile fields. Customers without email addresses require review before migration — HubSpot requires an email for full contact record creation, or a contact can be created without email and flagged for enrichment.

RedEye campaigns map to HubSpot deals when the campaign has an associated revenue or financial target. Campaign name becomes the deal name; campaign budget or target amount maps to the deal amount. Campaign identifiers are preserved in a custom field on the deal for traceability. For awareness campaigns without a revenue target, we recommend a dedicated 'Campaign Reference' custom property on contacts rather than deal records.

RedEye programs may represent enrollment-based logic (e.g., loyalty tiers, nurture programs). Each active program enrollment that has a commercial value maps to a HubSpot deal. Programs that track customer status without revenue (e.g., onboarding stage) are better expressed as custom contact properties with the program name as the property name and the enrollment status as the pick-list value.

RedEye records which customers are enrolled in which campaigns and programs as N:N associations. We map these to a HubSpot contact property capturing the campaign name and enrollment date, and link each campaign to a corresponding deal record when a revenue target exists. This preserves the 'enrolled in' relationship without creating a separate junction object.

RedEye email engagement events (opens, clicks, bounces) map to HubSpot engagement records associated with the contact. Each engagement records the campaign name, timestamp, and action type. HubSpot surfaces these as engagement timeline entries on the contact record. Original RedEye timestamps are preserved for reporting continuity.

RedEye event records (registrations and attendance) map to HubSpot meeting or call activities on the contact. The event name becomes the activity subject; attendance status (registered, attended, no-show) is captured in a custom property or activity notes field. Event dates are preserved as the activity start time.

RedEye product catalog records map to deal line items in HubSpot when available in the Sales Hub Professional tier. In Starter or basic tiers, product references are captured as custom properties on the deal record. We recommend evaluating HubSpot's product catalog setup before migration if product-to-deal linking is a core reporting requirement.

RedEye's behavioral scoring model has no native equivalent in HubSpot. We create a custom numeric property on the contact record (e.g., RedEye_Engagement_Score__c) and map the most recent score value at migration time. Scores update over time through HubSpot's own lead scoring workflows, which are rebuilt post-migration.

RedEye customer records may include an associated company or organization. These map to HubSpot company records with company name, domain, industry, employee count, and annual revenue fields. When a RedEye customer has no associated company, a 'No Company' placeholder company is created or the contact is flagged as unassociated for your admin to resolve.

RedEye campaign workflows, program enrollment triggers, and behavioral automation rules do not have a migration path to HubSpot. We export the full workflow definitions — trigger conditions, branch logic, channel steps, and timing rules — as a structured reference document that your team or a HubSpot partner uses to rebuild the automations inside HubSpot's workflow engine after migration.

Campaign configuration (sending domains, sender profiles, suppression lists, A/B test settings) is a RedEye platform configuration, not a data record. It cannot be exported and re-imported into HubSpot. Sending domain verification and sender profile setup must be reconfigured in HubSpot's email settings post-migration.