adobe-migration-deep-dive

name	adobe-migration-deep-dive
description	Execute major Adobe re-architecture: migrating from legacy Adobe APIs to Firefly Services, consolidating Creative Cloud integrations, and strangler-fig migration from competitor document/image APIs to Adobe. Trigger with phrases like "migrate adobe", "adobe migration", "switch to adobe", "adobe replatform", "replace with adobe".
allowed-tools	Read, Write, Edit, Bash(npm:*), Bash(node:*), Bash(kubectl:*)
version	1.0.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","design","adobe"]
compatible-with	claude-code

Adobe Migration Deep Dive

Overview

Comprehensive guide for three major migration scenarios: (1) legacy Adobe API consolidation into Firefly Services, (2) migrating from competitor document/image APIs to Adobe, and (3) JWT credential migration to OAuth Server-to-Server.

Prerequisites

• Current system documentation with API inventory
• Adobe Developer Console project with target APIs
• Feature flag infrastructure
• Rollback strategy tested in staging

Instructions

Migration Type Assessment

Type	From	To	Complexity	Duration
Auth migration	JWT credentials	OAuth Server-to-Server	Low	1-2 days
API consolidation	Separate PS/LR endpoints	Firefly Services SDK	Medium	1-2 weeks
Competitor replacement	Cloudinary/imgix/PDFTron	Adobe APIs	High	4-8 weeks
Full replatform	Custom pipeline	Adobe App Builder	High	2-3 months

Scenario 1: Consolidate to Firefly Services SDK

The Photoshop and Lightroom APIs were previously separate. They are now part of Firefly Services with a unified SDK:

// BEFORE: Separate clients for each API
import { PhotoshopAPI } from 'some-old-photoshop-client';
import { LightroomAPI } from 'some-old-lightroom-client';

// AFTER: Unified Firefly Services SDK
import { PhotoshopClient } from '@adobe/photoshop-apis';
import { LightroomClient } from '@adobe/lightroom-apis';
import {  }  ;


 config = {
  : process..!,
  :  (),
};

 photoshop =  (config);
 lightroom =  (config);
 firefly =  (config);