Migrate your Agillic data

Recipients is the primary person entity in Agillic. We export all standard fields (email, name, contact details) plus every custom recipient property defined in the client's schema. The schema is fully custom so we enumerate all fields during discovery before mapping.

The Recipients Export feature generates a snapshot file of all recipient records and their current field values. We use this as a baseline for full-contact migrations, then reconcile against API data for real-time accuracy.

Every send, open, click, bounce, SMS delivery, and event trigger is stored as an Activity record with a timestamp, recipient ID, and Flow Execution ID. We export Activity data per channel per date range to reconstruct engagement histories.

Agillic's Activity Export bundles all events for a given date range across channels into a structured file. We schedule exports spanning the customer's entire history, including Flow Execution IDs for journey reconstruction.

Flows are Agillic's campaign automation logic — essentially triggered workflows across channels. We export flow definitions as configuration records but Flows are tightly coupled to Agillic's execution engine; recreating equivalent automation in a destination platform requires workflow redesign.

Global Data Tables are custom relational data structures referenced within Flows. We export table schemas and all row data, then map to equivalent custom objects or lookup tables in the destination platform.

Content Blocks are modular HTML/text fragments used across multiple templates. We export block content and metadata; recombination in a destination CMS or email platform requires content refactoring.

Agillic Profiles aggregate all known data about a recipient across touchpoints. We treat Profile data as equivalent to the Recipient record with enriched attributes pulled from Activity and custom data.

Agillic can export micro-audience segments to Google and Meta in real time. We capture audience definitions and membership logic to recreate equivalent segments in the destination paid media activation layer.

Templates define layout and dynamic content fields for email, SMS, print, and push channels. We export template content and field mappings; HTML-based templates require conversion to the destination platform's template format.

The Flow Execution ID uniquely identifies each campaign trigger instance and is appended to Activity Exports when enabled. We preserve this ID to allow matching activity records back to specific workflow runs during migration validation.

Export Settings control file format (delimiter, extension, date format, timestamp format). We document the client's current export format configuration so we can match the destination's import requirements.