Migrate from Salla to Mrfqy: OAuth and CSV paths explained

Merchants expanding beyond Saudi Arabia often outgrow a KSA-only stack. Mrfqy's migration hub accepts Salla exports today via CSV and will add OAuth import through the official Salla Merchant API at api.salla.dev — the same API documented for product management and app partners.

What transfers from Salla

Products, variants, SKUs, prices, and bilingual titles map cleanly when you export from Salla admin or use the Merchant API list endpoints. Collections become Mrfqy collections; images download asynchronously into your media library.

Payment merchant IDs do not transfer — re-authorize Tap, Moyasar, or HyperPay under your Mrfqy store. Historical orders can archive as read-only records for accounting; live payment rails always require fresh credentials.

Use the Mrfqy migration hub

In admin, open Dashboard → Migrate, choose Salla, upload your export, preview mapped rows, then run the import job. The preview step catches duplicate SKUs and missing Arabic titles before anything writes to production.

Marketing guides at /migrate/salla walk through the same checklist with official Salla branding and links to Salla docs for merchants who prefer self-serve documentation.

Salla remains excellent for Saudi-only sellers. Mrfqy is the structural upgrade when your customers live in multiple Arab countries — import first, prove checkout, then repoint your domain.