Migrate your Front data

Conversations are Front's core unit. We export the full conversation record including all message segments, timestamps, channel source, assignee, status, and Inbox attribution. The structure maps cleanly to standard ticket objects in most destination systems.

Contacts export with name, email, phone, company, custom properties, and contact handles across channels. We map Front contact handles to standard email fields and preserve any linked company records.

Each message within a conversation is a distinct segment in Front. When migrating to a standard ticket system we flatten segments into a single thread body, preserving author, timestamp, and content. Rich formatting and inline attachments are handled per destination's capabilities.

Front Inboxes define which channels land where and who has access. We map Inboxes to Teams or Queues in the destination system but note that complex permission inheritance across Inboxes may require manual post-migration assignment review.

Teammates export with name, email, role, and assignment preferences. We match teammates by email address to the destination user directory. Custom role names may need field mapping depending on the destination's permission model.

Channels represent communication sources (email, chat, SMS, social, etc.). We export channel attribution so each conversation carries its origin. Note that Starter plan restricts to one channel, which affects migration volume scoping.

Tags are applied at conversation level. We export tags as flat labels and map them to the destination's tagging or labeling system. Tag hierarchy and tag-group organization do not carry over as structured taxonomy.

Front Rules are event-condition-action triggers. Migration requires manual rebuild in the destination system because conditional logic, delay steps, and action types vary significantly across platforms. We document all active Rules during discovery so customers can recreate them post-migration.

Front Workflows are multi-step process automations distinct from simple Rules. Workflows with conditions, branches, and delays require reimplementation in the destination platform. We export the workflow configuration as a reference document during scoping.

Front supports custom fields on application objects such as conversations and contacts. We export custom field definitions and values, but mapping requires understanding the destination's custom field schema and data type compatibility. Text, number, date, and dropdown fields map most reliably.

Front Analytics dashboards (Messages export, Full events export) use CSV format with timestamps in the requesting user's timezone. We export available analytics data but note that custom report configurations and dashboard layouts are not transferable across platforms.

Sequences are Front's automated outreach cadence tool. They include email templates, timing delays, and step logic. Sequence data and templates can be exported, but the automation engine must be recreated in the destination platform.

Translated knowledge base articles can be exported from Front. We preserve article content and structure; published status and category hierarchy require manual post-migration review in the destination.

Notes attached to conversations or contacts export with their text content and attribution. We map notes to the destination's equivalent internal note or comment field.