# Appmigrationkit

Transfer app data to or from other platforms using AppMigrationKit.

- Repository: https://github.com/dpearson2699/swift-ios-skills (1266 stars)
- Category: Testing
- License: see repository
- Last updated: 2026-07-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add dpearson2699/swift-ios-skills --skill appmigrationkit -g -a claude-code -y`
Codex: `npx skills add dpearson2699/swift-ios-skills --skill appmigrationkit -g -a codex -y`
Cursor: `npx skills add dpearson2699/swift-ios-skills --skill appmigrationkit -g -a cursor -y`
Gemini CLI: `npx skills add dpearson2699/swift-ios-skills --skill appmigrationkit -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add dpearson2699/swift-ios-skills`

## Description

Transfer app data to or from other platforms using AppMigrationKit. Use when implementing system-orchestrated one-time migration between iOS and Android or another platform, building an AppMigrationExtension, packaging transportable resources with ResourcesArchiver, importing resources on the destination device, reporting import progress, handling migration errors and app group cleanup, checking MigrationStatus, or testing migration code with AppMigrationTester.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# AppMigrationKit

One-time cross-platform data transfer for app resources. Enables apps to
export data to or import data from another platform (for example, Android)
during device setup or onboarding. AppMigrationKit APIs are iOS 26.0+ /
iPadOS 26.0+; the data-container entitlement is iOS 26.1+ / iPadOS 26.1+ /
Mac Catalyst 26.1+. Swift 6.3.

> **Beta-sensitive.** AppMigrationKit is new in iOS 26 and may change before GM.
> Re-check current Apple documentation before relying on specific API details.

AppMigrationKit uses an app extension model. The system orchestrates the
transfer between devices. The app provides an extension conforming to export
and import protocols, and the system calls that extension at the appropriate
time. The app itself never manages the network connection between devices.

## Contents

- [Architecture Overview](#architecture-overview)
- [Setup and Entitlements](#setup-and-entitlements)
- [App Migration Extension](#app-migration-extension)
- [Exporting Resources](#exporting-resources)
- [Importing Resources](#importing-resources)
- [Migration Status](#migration-status)
- [Progress Tracking](#progress-tracking)
- [Testing](#testing)
- [Common Mistakes](#common-mistakes)
- [Review Checklist](#review-checklist)
- [References](#references)

## Architecture Overview

AppMigrationKit operates through three layers:

1. **App extension** -- An `AppMigrationExtension` conforming type that the
   system invokes during migration. It handles data export and import.
2. **System orchestration** -- The OS manages the device-to-device session,
   transport, and scheduling. The extension does not control when it runs.
3. **Containing app** -- After migration completes, the app checks
   `MigrationStatus.importStatus` on first launch to determine whether
   migration occurred and whether it succeeded.

Key types:

The rest: https://github.com/dpearson2699/swift-ios-skills/blob/HEAD/skills/appmigrationkit/SKILL.md