Crossell Migration Checklist
A pre-flight before you move your marketplace catalog to Crossell.
1. Inventory your current state
- Count active listings per channel (Shopify, eBay, Trendyol, and other connected stores).
- Export a CSV of 50–100 representative rows (not your full catalog).
- Identify duplicates by SKU across channels.
- Note variants per parent (size, color, material, etc.).
- List the 5 channels you actively publish to today.
2. Decide your catalog shape
- Pick your source of truth: a PIM (Crossell) or a spreadsheet.
- Decide which fields are global vs channel-specific.
- Map your current field names to Crossell's canonical schema.
- Identify fields that need channel-specific overrides.
- Confirm you have product images (1+) for at least 80% of SKUs.
3. Audit channel-policy gaps
- Run the Crossell catalog-check on your sample CSV.
- Fix critical issues (missing required fields, policy violations).
- Address warnings (duplicate SKUs, suspicious pricing).
- Re-run the catalog-check; aim for an 80+ health score.
- Document any accepted risks (e.g. missing recommended fields).
4. Plan the migration window
- Pick a low-traffic window (typically Sunday 02:00–06:00 UTC).
- Notify any team members who touch listings during the window.
- Snapshot your source-platform state before starting.
- Decide the cutover strategy: parallel-run vs direct switchover.
- Prepare rollback plan (pause listings, restore from snapshot).
5. Execute the cutover
- Import catalog into Crossell (CSV or connector).
- Validate mapping rules per channel.
- Run a dry-run publish on 5–10 listings per channel.
- Fix any rejections before full publish.
- Publish remaining listings in batches.
6. Post-launch hygiene
- Monitor listing health scores for 7 days.
- Verify stock sync on a sample of SKUs.
- Confirm order routing still works on all channels.
- Archive the old tool export for audit.
- Schedule a 30-day review of pricing and limits.