VEYNDO
Handbook
extensions/apps/migration/README.mdView source ↗

English source · 2 min

Migration Assistant

Independent Rust source adapters, canonical records and a connected Veyndo Studio. Read the workflow, current coverage and deployment guide. App-specific code stays here; Core contains only generic native import/job admission.

  • contract/: stable versioned source identities and exact source money.
  • adapters/: source-owned normalization, languages, addresses, historical lines/dates.
  • service/: bounded immutable export packaging/HTTPS reads, separate export credentials, complete source-page evidence, complete concrete WooCommerce families, byte-bounded variant slices and native inspection/import jobs.
  • studio/: source setup, review, native saved work plans, durable reviewed-page records, ordered continuation and current-field comparison and the shared agent drawer.
  • tests/: real Rust protocol/Core fixtures and app-owned UI acceptance.

Native target import currently covers private products and original images, categories, editable content pages, CRM customers, immutable historical orders, moderated reviews and inactive native coupons. Reviews never acquire fabricated purchase verification; supported WooCommerce coupons require explicit native activation review and retain their original currency and remaining-use snapshot. Slow source inspections run in the existing saved jobs and can be reopened after reload. Products use real native variant/category associations and the existing native tax calculator for explicitly reviewed net source prices; all private domains can share one selected preview. Normalizing other source domains does not implement their target migration. Do not advertise complete theme/plugin conversion or zero-downtime cutover.

CRM intake now retains native billing/shipping/additional addresses (maximum 50), original subdivisions and historical invoice/delivery addresses. Shopware summaries are expanded through bounded detail reads; Presta ownership/geography/currency references are checked; Shopify full-history access is explicitly required. Source PII stays behind current paired rights, with no new login or ordinary address-change workflow. See the main guide for provider shapes and remaining acceptance.

migration-assistant pack produces a private checksum-bound package from original expanded JSON lines; configured HTTPS readers use the same reviewed native jobs. See the guide for the command, encrypted export settings, source-reference checks and explicit distinction between immutable domain bytes and whole-shop cutover.

Saved plans now walk supported domains and source cursors with explicit per-page approval. Their exact reviewed intents and bounded current-native-field reports use private logical records; archiving technical jobs or restarting the service does not erase them. A read-only reconciliation job cannot create even a missing target. Differences remain visible and are never silently repaired. Product stock, unsupported mappings, source-wide final deltas/cutover and public hosting acceptance remain separate. No new table or queue is introduced.

Product HTML uses the same bounded native document parser as authored pages. A plain summary accompanies the editable native rich description; generic Core intake maps current language keys and compares source-owned rich content during reconciliation. Original imported snapshots retain explicit review/conflict rules. tests/woocommerce-live/ contains the actual disposable WordPress/WooCommerce source recipe. See docs/evidence/woocommerce-source-2026-10-29.md for interruption, all eight areas, replay and browser purchase acceptance.