Service
Most centres looking at Defyn SAM are already running something — manual CSV uploads, a custom developer-built script, or a competing plugin that's stopped getting updates. The fear isn't trying something new; it's losing the data and momentum you already have. Our migration service lines up a parallel-run period so the cutover is gradual and reversible.
We've migrated centres from CSV-export workflows, custom Python scripts, two different competing plugins, and one home-grown PHP integration. The process is the same every time:
We ask for a screenshare of your current sync setup and a read-only export of your WC / Shopify catalogue. We identify the boundaries — what's SAM-sourced, what's manual, what's hybrid.
Defyn SAM installs alongside the old system in read-only mode. We sync the full SAM catalogue to a staging URL. You verify the staging output matches expectations before any production change.
Edge cases surface: products that exist in WC but not in current SAM, manually-edited descriptions you want preserved, custom categories. We document each and decide per case — keep, sync over, or merge.
Scheduled at a low-traffic window (typically Sunday night Sydney time). Old system disabled. Defyn SAM flipped to write mode. First production sync runs. Test orders placed to confirm the end-to-end flow.
24 hours of monitored operation: Defyn engineer on call, every sync run reviewed in real time, any anomaly investigated within minutes. Stable after 24h.
Team walkthrough of the new dashboard. Old-system credentials revoked. Migration sign-off. The 30-day priority support window kicks in from this date.
Scenario: Centre running a custom Python script written by a former staff developer. Script worked but nobody knew how to update it.
Result: We mapped the script's data flow to Defyn SAM's syncers, confirmed feature parity, then ran 14 days of parallel sync. After cutover the script was retired. Catalogue history preserved 100%.
Scenario: Centre on a competing plugin whose vendor stopped responding to support tickets in late 2025.
Result: Old plugin disabled. Defyn SAM imported the existing WC product catalogue (matched by sam_id meta where present, by SKU otherwise). Manual products untouched. Zero downtime — shop stayed live throughout.
Scenario: Centre running CSV export-import every Friday. Manual workflow ate 4 hours/week from the coordinator.
Result: Defyn SAM replaced the CSV cycle. Coordinator now spends 0 hours/week on catalogue sync. The Friday morning ritual is gone.
During the audit phase we flag every product where the SAM-source content differs from what's live on your storefront. You decide per product — keep your manual edits, take SAM as source of truth, or merge. We don't overwrite anything you haven't approved.
Yes — Defyn SAM doesn't touch WC's order tables. Existing orders stay exactly as they are. Defyn SAM only governs how new orders push to SAM going forward.
Three weeks end-to-end is typical. Smaller centres with cleaner data can cut over inside two weeks; large catalogues with messy historical state can stretch to four. We don't accelerate at the expense of safety.
Yes. Phase 2 is specifically designed for this — Defyn SAM is installed in read-only mode (writes to staging, not production) while your existing system continues to drive the live storefront. No conflicts, no downtime.
Tailored to complexity. The cleanest path is a discovery call where we look at your current setup; from there we can quote concretely.
Want a 15-minute screenshare against your actual SAM data? Send us a quick note or call — we’ll line up a walkthrough at a time that suits.
