Upgrade the sender first

1. Back up both databases and plugin folders; update installed plugin files without uninstalling.
2. Deploy the 1.11 sender first, then the receiver. Restart and complete normal migration/update steps on both.
3. Enable Publisher Mode on the source and Receiver Mode on the destination as appropriate.
4. Retain the authorized client profile/API key and allowed vendors. Save the receiver source configuration and run Test Saved Connection.
5. After a small successful import, confirm product fields, mappings, pictures, and Sync History.

A connection test checks samples. It does not certify every catalog record or image. Category images and source-filtered pagination require the 1.11 sender.

Browse and preview selected changes

1. Open Available Products on the receiver; search by SKU/name and select an exact vendor when needed.
2. Include existing SKUs if you need to review updates. Select up to 100 products.
3. Choose Preview Selected Changes and review Create, Update, Skip, Blocked, and Resume results plus mapping/image actions.
4. Resolve duplicate or ambiguous identities, then queue eligible products.
5. Review Background Import Jobs and the final storefront/Sync History results.

Selected preview scans the permitted feed across pages to detect duplicate SKUs. It makes no receiver catalog changes and downloads no image content. It does not freeze source values; changed settings/source configuration require another preview.

Background jobs and recovery

Full imports, selected work, scheduled pulls, and targeted repairs use durable background jobs. Completed catalog steps and recovery checkpoints are retained. Cancellation stops at checkpoints and keeps completed changes; resume retries unfinished items using saved choices and current authorized source data.

1. Inspect failed items under Background Import Jobs and Incomplete Imports / Retry.
2. Correct the reported source, identity, mapping, or image problem.
3. Resume/retry the affected work and verify its result.
4. Do not assume a plugin-file rollback reverses imported catalog data.

Recovery begins with work started under 1.09 or later. Older incomplete work cannot be reconstructed automatically. An interrupted step may run again; the entire product import is not one all-or-nothing transaction.

Product, manufacturer, and category images

Image replacement validates replacements before removing old product mappings, and shared picture binaries are preserved. Manufacturer repair is separate from ordinary product-import recovery.

1. Enable Sync Category Images on the sender to publish mapped category and ancestor pictures.
2. Enable it on the receiver for category images during full/selected imports. Import category mappings too when categories do not exist.
3. Use Repair Category Images for existing categories matched by the complete category path.
4. Leave Replace existing category images from source off initially; enable it only when intentional replacement is needed.
5. Inspect failed/absent picture counts in Sync History.

Dedicated category repair is independent of the receiver's Sync Category Images option. Duplicate paths, duplicate sibling names, changed identities, or missing categories need review. Category names containing > cannot be represented unambiguously in the path format.

Scope and rollout checks

Queue All Matching Products uses vendor and SKU/name search across all pages. Targeted image/specification/manufacturer repairs use vendor scope across pages and ignore product search. Existing-SKU visibility only affects the browsing page; it does not narrow the full queued import.

Test a small selection before a full run. Verify Sync Product Content before allowing replacements of existing names/descriptions/SEO fields, and confirm source/receiver templates and specifications.