Guide
Migrate Your Product Catalog to SoundSync
Product migration is supported through public storefronts, product pages, and CSV, TSV, XLSX, or JSON exports.
Product migration is supported
Move your product catalog to SoundSync from another platform using a public store URL, an individual product page, or a CSV, TSV, XLSX, or JSON product export. Bring over supported product information, artwork, public audio, video references, and authorized delivery files, then review everything before publishing.
Importing creates drafts, never a live catalog. Select which products to save, correct the details, attach private delivery files, configure licensing, and publish only when ready. An export can stand alone when a source store cannot be read.
SoundSync
Add the private files after reviewing the import
The delivery step lets you select multiple installers or archives and review their product matches. Its resume guidance applies to this importer; public promotional media and customer-authorized downloads remain separate workflows.
SoundSync
Bring an existing catalog into the product workflow
Start from a store URL, an export, or both, then review the products and media before saving drafts. The downloadable examples help prepare an export. This product-import workflow does not move customer passwords, payment methods or every account record.
Move from your current platform
Whether you are moving from Gumroad, Shopify, WooCommerce, or another store, use a public catalog/product URL or a supported product export. The importer is not limited to a single source platform. When a source blocks discovery or depends on JavaScript, use an export or prepare the supplied CSV format instead.
SoundSync
From source catalog to SoundSync drafts
-
Choose a source
Open Import/Upload from Products or onboarding. Use a store URL for a catalog, or a product URL to create or fill a single draft. Add a product export when useful.
-
Review the mapping
Map export columns and select a SoundSync product type. Confirm prices as USD amounts; SoundSync does not convert source currencies.
-
Choose products and media
Edit the proposed copy and price, select the products, and copy selected images and public audio into SoundSync storage. Videos remain supported provider embeds.
-
Save drafts
Review warnings and confirm. Existing matches are not selected automatically; explicitly allow filling missing fields in matched drafts.
-
Prepare delivery and access
Match direct download links or upload files privately. Check pricing, licensing, compatibility, bundle membership, and storefront presentation before publication.
Your saved work stays yours
Source mappings help repeated imports find the same product. Existing names, descriptions, prices (including a deliberate free price), media, and attached files are preserved. Filling an existing draft adds missing information rather than overwriting your work. Published products are skipped; edit their public content through the normal product workflow.
A paid source price below $9.99 remains visible for review, but the draft selling price is left unset. It is not silently converted to free. Set a valid paid price before publication.
SoundSync
Prepare your catalog
Plan the account and billing transition
Product migration brings catalog information and supported files into SoundSync. Customer accounts, historical orders and payments, active subscription payment authority, and marketing consent do not transfer automatically with a product catalog. Keep existing recurring billing in place until you have arranged the appropriate customer-authorized transition.
Approved external-order, customer, serial, and entitlement workflows have separate requirements. Configure imported bundle membership and licensing deliberately; a source description does not establish a SoundSync product relationship or entitlement.
Plugin package updates
Use the HISE/JUCE regeneration and release guides to connect your imported products to the intended package. Rebuilding a package updates its integration; it does not move a customer's existing payment mandate or create marketing permission.
Customer identity in redeemed-serial imports
Redeemed-serial imports, through the CSV upload or legacy JSON route, reuse the existing customer identity matched by normalized email without replacing its shared name, verification, account status or marketing preferences. A new identity is created only as part of a successful imported serial row. The serial can retain its developer-specific imported name snapshot; that snapshot is not a shared account-profile edit.
Unknown or unowned products, invalid required input and duplicate serials are skipped. A duplicate race or failed serial insert rolls back any customer created for that row. Earlier successful rows can remain imported if a later row fails; review the result and retry deliberately. A serial import is not a paid checkout, inbox verification, login transfer or permission to bypass an unsubscribe.
SoundSync
