Migrate your ActiveTrail data

Contacts are the primary data unit in ActiveTrail. Each record holds email address, subscription status, behavioral tags, and custom field values. The API exposes contact read/write endpoints. We migrate contacts as standard record imports, preserving subscription status flags and custom properties. Deduplication logic applies email-based matching by default.

Segments are dynamic contact groups built on filter conditions (demographics, behavior, engagement). The segment definition structure is exported as a rule set and rebuilt at the destination. Static segment membership is migrated as bulk contact assignments. Dynamic re-evaluation of segment rules must be confirmed post-migration.

Journeys are multi-step workflows with triggers, conditions, delays, and channel actions (email, SMS, WhatsApp). The visual automation graph is reconstructed at the destination using equivalent actions. Trigger events (form submission, tag applied, date-based) are re-mapped to destination equivalents. Live-running journeys cannot be migrated as active — they are exported as dormant blueprints and reactivated manually.

Campaigns are one-off or recurring email sends with subject, body content, sender identity, and scheduling. Campaign metadata (name, status, send time, audience) migrates directly. HTML template content is exported as raw markup and imported as a template asset at the destination. Engagement stats (opens, clicks) are exported as historical records.

SMS campaigns operate similarly to email campaigns but with character-count and phone number validation constraints. Phone number format normalization (E.164) is applied during migration. SMS-specific compliance fields (consent records) are mapped to the destination's opt-in mechanism.

Landing pages built within ActiveTrail's builder are exported as HTML or reconstructed using page builder imports where the destination supports it. Form fields embedded in landing pages are mapped to destination equivalent fields. Standalone page URLs are preserved as redirects or rebuilt depending on destination capabilities.

Signup forms capture new contacts into lists or trigger automation entry points. Form field definitions are exported and rebuilt at the destination. The connection between form submission and list/automation enrollment is re-established using destination triggers.

ActiveTrail's survey tool creates interactive questionnaires embedded in emails or landing pages. Survey structure (questions, answer options, conditional logic) is exported and rebuilt. Survey response data is migrated as contact property updates or linked records depending on destination schema.

Custom contact fields store supplemental data (company size, preferences, purchase history). Field types (text, number, date, dropdown) are mapped to destination equivalents. Dropdown fields require value mapping between ActiveTrail's option set and the destination's option set. Field-level permissions are not migrated.

Tags are behavioral labels applied to contacts for segmentation and journey triggering. Tag names are migrated as flat string assignments. Where the destination uses a different tagging taxonomy, we map active tags to the closest equivalent or create new ones on the fly.

Email template assets (HTML, images, styles) are exported from ActiveTrail's library and imported as brandable templates at the destination. Inline CSS and image hosting references are updated to point to the destination's asset CDN.