Custom Fields is also available as a SAM feature but works differently from the exporters below. See the Custom Field Values Reference for details.

Overview

Each exporter packages a specific type of data:

Exporter	What It Exports	When to Use
Mappings	ID mappings between DC and cloud objects	Map DC IDs to cloud IDs (issues, pages, users, etc.)
Binary	Files stored in the Jira Home directory on DC	Migrate app-owned files (attachments, uploads, assets)
AO Tables	Active Objects database tables	Migrate structured app data stored in AO tables

How data is delivered:

Direct data to you: Mappings, AO tables - event files contain the actual records
Metadata + download: Binary files - event files contain metadata with fileId, you download the actual bytes separately

Mappings

Mappings Reference

What: ID mappings between Data Center and cloud objects (issues, pages, users, projects, spaces).

How it works:

Exported after product migration completes
Direct data: Event files contain the actual mapping records (no additional downloads needed)
Contains old DC IDs → new cloud IDs
Enables apps to link migrated data to correct cloud objects

Use cases:

Map issue comments to cloud issues
Link page attachments to cloud pages
Associate user data with cloud accounts

Example data:

1
2
3
4
5
6
{
  "targetCloudId": "10042",
  "sourceServerId": "12345",
  "targetType": "jira:issue"
}

Binary

Binary Reference

What: Files from your app's directories in the Data Center home directory.

How it works:

Exported before and during product (Jira/Confluence) migration
Specify directory prefixes your app owns
Two-step download: Event files contain metadata (filepath, fileId), then you download actual bytes using the fileId
Supports incremental updates and deletions

Use cases:

Migrate uploaded attachments
Transfer app-generated reports
Move cached assets or thumbnails

Example configuration:

1
2
3
4
5
6
7
modules:
  migration:managedExports:
    - key: binary
      directoryPrefix:
        - "uploads/my-app"
        - "assets/my-app-files"

AO Tables

AO Reference

What: Structured data from Active Objects database tables.

How it works:

Exported during migration
Direct data: Event files contain the actual AO table records (no additional downloads needed)
Specify table names to export
Data delivered as JSONL records
Supports incremental updates and deletions (via TXN_SEQUENCE)

Use cases:

Migrate data from database tables including Atlassian stored data like entityproperties
Transfer business logic state
Move structured data models

Example configuration: TBD

Choosing Exporters

Select exporters based on your DC app's data:

App has AO tables? → Enable AO exporter
App stores files? → Enable Binary exporter
App needs object IDs? → Enable Mappings exporter

You can enable multiple exporters by declaring them in your manifest:

1
2
3
4
5
6
7
modules:
  migration:managedExports:
    - key: mapping
      entityTypes: ["jira:issue", "confluence:page"]
    - key: binary
      directoryPrefix: ["uploads/my-app"]

Export Timing

Started before and during product migration

Binary

Started during product migration:

AO Tables

After product migration:

Mappings (requires cloud IDs to exist)

Next Steps

Lifecycle Integration - Understand how SAM works
Quick Start - Try the mappings exporter
Reference Documentation - Detailed specs for all exporters