Migrate your RedEye data
B2C lifecycle marketing automation platform built for retailers, travel, and financial services, with a contact-count pricing model and multi-channel campaign orchestration.
In its favor
Why people choose RedEye
The signal that keeps RedEye on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Dedicated IP and inbox monitoring included on all tiers makes RedEye attractive to senders who prioritise email deliverability above all else.
Unlimited email sends and events stored means high-volume retail marketers can run frequent promotions without per-campaign cost anxiety.
Multi-channel orchestration with up to nine channels in one platform reduces the need for a fragmented marketing stack across email, SMS, and push.
Strong account management and dedicated support contacts on both Essentials and Elevate tiers keep mid-market B2C teams from feeling like they are self-served.
AI predictive analytics and customer lifetime value modelling on the Elevate plan appeals to data-driven marketers who want automated insight without a separate BI tool.
Contact database size is capped per tier (150,000 on Essentials) and upselling to higher volumes can arrive without warning, making growth-stage brands feel price-pressured.
Reporting dashboards are described as basic by power users who want deeper drill-down and custom analytics beyond the built-in charts and dashboards.
The platform has a learning curve; reviewers note that initial onboarding guidance is insufficient and some features take time to master without better in-app documentation.
Drag-and-drop campaign building and auto-save functionality are absent, creating friction for marketers accustomed to more modern no-code UX patterns.
Reasons to switch
Why people leave RedEye
The recurring reasons buyers give for replacing RedEye. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where RedEye fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
RedEye pricing overview
RedEye uses a monthly subscription model priced from £1,000/month for Essentials and £1,500/month for Elevate. Pricing is anchored to contact database size and channel count rather than per-seat user licensing, making it more predictable for marketing teams but creating hard ceilings as the contact list grows.
Essentials
Tier 1 of 2
£1,000/month (starting)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on RedEye's schedule — see our quote-based pricing →
What gets migrated
RedEye object support
Object-by-object support for RedEye migrations. Per-pair details surface during scoping.
Contacts
Mapping requiredContact records are the core object in RedEye, deduplicated via a unique customer identifier with behavioural enrichment. We preserve all standard contact properties but flag any contacts exceeding the destination tier's 150,000-contact ceiling as they will trigger a billing upgrade.
Companies/Accounts
Mapping requiredRedEye's B2C model treats contacts as the primary record; company linkage exists but is lighter-weight than enterprise CRM models. We map company associations as a custom contact property when the destination platform expects full Account records.
Campaigns
Fully supportedCampaigns migrate cleanly as structured objects with their channel assignments, timing rules, and goal metrics intact. We sequence campaign dependencies before import so triggered campaigns do not fire against an incomplete contact list.
Customer Journeys
Mapping requiredJourneys are visual workflow definitions with branching logic tied to contact behaviours and lifecycle stages. We export the journey tree structure and rebuild it in the destination platform using equivalent conditional logic, noting that no-code journey builders vary significantly between vendors.
Events
Fully supportedBehavioural events stored in RedEye (website actions, email opens, purchase triggers) migrate as a flat event log. We preserve event timestamps and contact associations so downstream platforms can reconstruct behavioural timelines.
Product Records
Fully supportedProduct catalogue records migrate as a structured object with SKU, name, pricing, and category fields. Unlimited product records are included on both Essentials and Elevate tiers.
Channels
Mapping requiredRedEye supports email plus up to eight additional channels. We map channel assignments at the campaign level and flag any channels not natively supported by the destination platform for manual configuration post-migration.
Custom Fields
Mapping requiredCustom contact and event fields require explicit field-to-field mapping during scoping. We extract the full field schema from RedEye and match it against the destination's custom property model before import.
Segments
Mapping requiredSegments are dynamic contact groups based on behavioural rules and demographic criteria. We export segment definitions as rule sets and rebuild them in the destination using equivalent filter logic.
Reports and Dashboards
Not in this platformRedEye's native reporting dashboards use proprietary visualisation components that do not export. We migrate the underlying contact, event, and campaign performance data so reports can be rebuilt from scratch in the destination platform.
Attachments
Fully supportedCampaign assets such as images and documents attached to campaigns or emails migrate via file export and re-upload. We preserve the file hierarchy and naming conventions to minimise manual re-linking.
Tags
Fully supportedContact and campaign tags migrate as a flat tag array. We map tag names exactly and flag any tag characters unsupported by the destination platform's schema.
| Object | Support | Notes |
|---|---|---|
| Contacts | Mapping required | Contact records are the core object in RedEye, deduplicated via a unique customer identifier with behavioural enrichment. We preserve all standard contact properties but flag any contacts exceeding the destination tier's 150,000-contact ceiling as they will trigger a billing upgrade. |
| Companies/Accounts | Mapping required | RedEye's B2C model treats contacts as the primary record; company linkage exists but is lighter-weight than enterprise CRM models. We map company associations as a custom contact property when the destination platform expects full Account records. |
| Campaigns | Fully supported | Campaigns migrate cleanly as structured objects with their channel assignments, timing rules, and goal metrics intact. We sequence campaign dependencies before import so triggered campaigns do not fire against an incomplete contact list. |
| Customer Journeys | Mapping required | Journeys are visual workflow definitions with branching logic tied to contact behaviours and lifecycle stages. We export the journey tree structure and rebuild it in the destination platform using equivalent conditional logic, noting that no-code journey builders vary significantly between vendors. |
| Events | Fully supported | Behavioural events stored in RedEye (website actions, email opens, purchase triggers) migrate as a flat event log. We preserve event timestamps and contact associations so downstream platforms can reconstruct behavioural timelines. |
| Product Records | Fully supported | Product catalogue records migrate as a structured object with SKU, name, pricing, and category fields. Unlimited product records are included on both Essentials and Elevate tiers. |
| Channels | Mapping required | RedEye supports email plus up to eight additional channels. We map channel assignments at the campaign level and flag any channels not natively supported by the destination platform for manual configuration post-migration. |
| Custom Fields | Mapping required | Custom contact and event fields require explicit field-to-field mapping during scoping. We extract the full field schema from RedEye and match it against the destination's custom property model before import. |
| Segments | Mapping required | Segments are dynamic contact groups based on behavioural rules and demographic criteria. We export segment definitions as rule sets and rebuild them in the destination using equivalent filter logic. |
| Reports and Dashboards | Not in this platform | RedEye's native reporting dashboards use proprietary visualisation components that do not export. We migrate the underlying contact, event, and campaign performance data so reports can be rebuilt from scratch in the destination platform. |
| Attachments | Fully supported | Campaign assets such as images and documents attached to campaigns or emails migrate via file export and re-upload. We preserve the file hierarchy and naming conventions to minimise manual re-linking. |
| Tags | Fully supported | Contact and campaign tags migrate as a flat tag array. We map tag names exactly and flag any tag characters unsupported by the destination platform's schema. |
Gotchas
What to watch for in RedEye migrations
Issues we've hit on past RedEye migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Contact database size limits differ by pricing tier
Campaign journey logic does not export as a portable schema
Reports and dashboards are not exportable
| Severity | Issue |
|---|---|
| High | Contact database size limits differ by pricing tier |
| Medium | Campaign journey logic does not export as a portable schema |
| Medium | Reports and dashboards are not exportable |
Leaving RedEye?
Where RedEye customers move next
12 destinations RedEye can migrate to.
How a RedEye migration works
Four steps, RedEye-specific
Connect
Not publicly documented into RedEye. Scopes limited to read-only on the data we move.
Map
We translate RedEye-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate RedEye quirks before production.
Migrate
Full migration with RedEye rate-limit handling. Rollback available throughout.
FAQ
RedEye migration FAQ
Answers to the questions buyers ask most during RedEye migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your RedEye migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate RedEye.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your RedEye setup and destination — written quote back within a business day.