flexport-migration-deep-dive
Execute major migration strategies for Flexport including migrating from legacy freight forwarders, ERP system integration, and strangler fig patterns. Trigger: "flexport migration", "migrate to flexport", "flexport ERP integration".
Best use case
flexport-migration-deep-dive is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Execute major migration strategies for Flexport including migrating from legacy freight forwarders, ERP system integration, and strangler fig patterns. Trigger: "flexport migration", "migrate to flexport", "flexport ERP integration".
Teams using flexport-migration-deep-dive should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/flexport-migration-deep-dive/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How flexport-migration-deep-dive Compares
| Feature / Agent | flexport-migration-deep-dive | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Execute major migration strategies for Flexport including migrating from legacy freight forwarders, ERP system integration, and strangler fig patterns. Trigger: "flexport migration", "migrate to flexport", "flexport ERP integration".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Flexport Migration Deep Dive
## Overview
Guide for migrating to Flexport from legacy freight forwarders, manual spreadsheet workflows, or other logistics platforms. Uses a strangler fig pattern to gradually move operations to the Flexport API while maintaining existing systems.
## Migration Scenarios
| From | To | Complexity | Timeline |
|------|----|-----------|----------|
| Spreadsheet/email | Flexport API | Low | 2-4 weeks |
| Legacy freight forwarder API | Flexport API | Medium | 4-8 weeks |
| ERP (SAP, Oracle) | ERP + Flexport | High | 8-16 weeks |
| Multiple forwarders | Flexport consolidated | High | 6-12 weeks |
## Instructions
### Phase 1: Data Migration — Product Catalog
```typescript
// Migrate product catalog from legacy system to Flexport Product Library
async function migrateProducts(legacyProducts: LegacyProduct[]) {
const results = { success: 0, failed: 0, errors: [] as string[] };
for (const legacy of legacyProducts) {
try {
await fetch('https://api.flexport.com/products', {
method: 'POST',
headers,
body: JSON.stringify({
name: legacy.description,
sku: legacy.partNumber,
hs_code: legacy.tariffCode,
country_of_origin: legacy.originCountry,
unit_cost: { amount: legacy.unitCost, currency: legacy.currency },
weight: { value: legacy.weightKg, unit: 'kg' },
}),
});
results.success++;
} catch (err) {
results.failed++;
results.errors.push(`${legacy.partNumber}: ${err}`);
}
}
console.log(`Products migrated: ${results.success}/${legacyProducts.length}`);
return results;
}
```
### Phase 2: Strangler Fig — Dual-Write
```typescript
// During migration, write to both systems
class DualWriteShipmentService {
constructor(
private legacy: LegacyForwarderClient,
private flexport: FlexportClient,
private featureFlags: FeatureFlags,
) {}
async createBooking(params: BookingParams) {
// Always write to legacy during migration
const legacyResult = await this.legacy.createBooking(params);
// Write to Flexport if enabled for this route
if (this.featureFlags.isEnabled('flexport_booking', { route: params.route })) {
try {
const fpResult = await this.flexport.createBooking(params);
// Compare results for validation
this.compareResults(legacyResult, fpResult);
} catch (err) {
// Log but don't fail — legacy is still primary
logger.warn({ err, route: params.route }, 'Flexport dual-write failed');
}
}
return legacyResult; // Legacy is source of truth during migration
}
}
```
### Phase 3: Cutover — Route by Route
```typescript
// Migrate routes one at a time, validate, then cut over
const MIGRATION_PHASES = [
{ routes: ['CNSHA-USLAX'], startDate: '2025-04-01', description: 'Shanghai-LA (highest volume)' },
{ routes: ['CNSHA-DEHAM', 'CNSHA-NLRTM'], startDate: '2025-05-01', description: 'Asia-Europe' },
{ routes: ['*'], startDate: '2025-06-01', description: 'All remaining routes' },
];
// Validate migration readiness per route
async function validateRoute(route: string): Promise<{
productsCovered: boolean;
webhooksWorking: boolean;
dataParity: boolean;
}> {
// Check all products on this route exist in Flexport
const products = await db.products.findMany({ where: { routes: { has: route } } });
const fpProducts = await flexport('/products?per=100');
const fpSkus = new Set(fpProducts.data.records.map((p: any) => p.sku));
const productsCovered = products.every(p => fpSkus.has(p.sku));
return { productsCovered, webhooksWorking: true, dataParity: true };
}
```
### Phase 4: Decommission Legacy
```typescript
// After all routes migrated and validated
async function decommissionLegacy() {
// Final data sync — export all historical data
const allShipments = await legacy.exportAllShipments();
await archiveToS3(allShipments, 'legacy-forwarder-archive');
// Disable legacy API keys
// Remove dual-write code paths
// Update monitoring to Flexport-only alerts
logger.info('Legacy forwarder decommissioned');
}
```
## Migration Checklist
- [ ] Product catalog migrated and validated
- [ ] Purchase order history exported
- [ ] Webhook endpoints configured and tested
- [ ] Dual-write enabled for first route
- [ ] Data parity validated between systems
- [ ] Stakeholders notified of cutover schedule
- [ ] Rollback procedure documented and tested
- [ ] Legacy system archived (not deleted)
## Resources
- [Flexport Developer Portal](https://developers.flexport.com/)
- [Flexport API Reference](https://apidocs.flexport.com/)
- [Products API Tutorial](https://developers.flexport.com/tutorials/products-api-tutorial/)
## Next Steps
This completes the Flexport skill pack. Start with `flexport-install-auth` for new integrations.Related Skills
workhuman-upgrade-migration
Workhuman upgrade migration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman upgrade migration".
wispr-upgrade-migration
Wispr Flow upgrade migration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr upgrade migration".
windsurf-upgrade-migration
Upgrade Windsurf IDE, migrate settings from VS Code or Cursor, and handle breaking changes. Use when upgrading Windsurf versions, migrating from another editor, or handling configuration changes after updates. Trigger with phrases like "upgrade windsurf", "windsurf update", "migrate to windsurf", "windsurf from cursor", "windsurf from vscode".
windsurf-migration-deep-dive
Migrate to Windsurf from VS Code, Cursor, or other AI IDEs with full configuration transfer. Use when migrating a team to Windsurf, transferring Cursor rules, or evaluating Windsurf against other AI editors. Trigger with phrases like "migrate to windsurf", "switch to windsurf", "windsurf from cursor", "windsurf from copilot", "windsurf evaluation".
webflow-upgrade-migration
Analyze, plan, and execute Webflow SDK upgrades (webflow-api v1 to v3) with breaking change detection, API v1-to-v2 migration, and deprecation handling. Trigger with phrases like "upgrade webflow", "webflow migration", "webflow breaking changes", "update webflow SDK", "webflow v1 to v2".
webflow-migration-deep-dive
Execute major Webflow migrations — from other CMS platforms to Webflow CMS, between Webflow sites, or large-scale content re-architecture using the Data API v2 bulk endpoints, strangler fig pattern, and data validation. Trigger with phrases like "migrate to webflow", "webflow migration", "import into webflow", "webflow replatform", "move content to webflow", "webflow bulk import", "wordpress to webflow".
vercel-upgrade-migration
Upgrade Vercel CLI, Node.js runtime, and Next.js framework versions with breaking change detection. Use when upgrading Vercel CLI versions, migrating Node.js runtimes, or updating Next.js between major versions on Vercel. Trigger with phrases like "upgrade vercel", "vercel migration", "vercel breaking changes", "update vercel CLI", "next.js upgrade on vercel".
vercel-migration-deep-dive
Migrate to Vercel from other platforms or re-architecture existing Vercel deployments. Use when migrating from Netlify, AWS, or Cloudflare to Vercel, or when re-platforming an existing Vercel application. Trigger with phrases like "migrate to vercel", "vercel migration", "switch to vercel", "netlify to vercel", "aws to vercel", "vercel replatform".
veeva-upgrade-migration
Veeva Vault upgrade migration for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva upgrade migration".
veeva-migration-deep-dive
Veeva Vault migration deep dive for enterprise operations. Use when implementing advanced Veeva Vault patterns. Trigger: "veeva migration deep dive".
vastai-upgrade-migration
Upgrade Vast.ai CLI, migrate API versions, and handle breaking changes. Use when upgrading vastai CLI, detecting deprecations, or migrating between API versions. Trigger with phrases like "upgrade vastai", "vastai migration", "vastai breaking changes", "update vastai CLI".
vastai-migration-deep-dive
Migrate GPU workloads to or from Vast.ai, or between GPU providers. Use when switching from AWS/GCP/Azure GPU instances to Vast.ai, migrating between GPU types, or re-platforming ML infrastructure. Trigger with phrases like "migrate to vastai", "vastai migration", "switch to vastai", "vastai from aws", "vastai from lambda".