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".
What this skill does
# 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 in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.