Jumpseller preparation should define how the Source Store will be represented through parent Products, variants, customer-entered options, custom fields, Categories, filters, navigation, inventory, Customers, Customer Categories, Orders, content, URLs, applications, and external systems. A source attribute system may contain all of those meanings in one table, so preparation must classify the business role before deciding the destination.
The preparation package should identify the owner, evidence, and ready condition for each important relationship. It should make the representative migration sample set representative and traceable to source evidence.
Confirm the Jumpseller Store Scope
Record the destination assumptions that affect data preparation.
| Area | Preparation decision | Ready evidence |
|---|---|---|
| Product identity | Which source records become parent Products and which become variants | Product-family and SKU matrix |
| Product inputs | Which source values generate variants, collect Customer input, or describe the Product | Option and custom-field classification |
| Discovery | Which source groups become Categories, filters, navigation, or landing content | Category and navigation outline |
| Inventory | Whether stock belongs to Products, variants, locations, or an external system | Inventory authority map |
| Customer context | Which account, category, pricing, consent, and external-ID relationships remain | Customer relationship inventory |
| Content and routes | Which pages, Blog Posts, Product/Category content, menus, and redirects remain | Content and URL inventory |
Where multiple languages, currencies, domains, shipping regions, or sales channels are relevant, record the intended scope and owner before preparing localized content and route evidence. Product, Category, content, price, and inventory decisions should use the same scope definitions so records do not appear in a market or channel without the supporting commercial context.
Prepare Access, Exports, and Source Backups
Collect the source and Jumpseller access needed to retrieve and interpret the in-scope records, together with recoverable evidence of the Source Store.
Prepare:
- administrator access to the Source Store and Jumpseller Store;
- Product and inventory exports, including variant identifiers and stock where available;
- Customer and Order exports or reports;
- Category, content, SEO, and URL lists;
- media and downloadable files when source URLs may expire or require authentication;
- Customer Category, price-list, and volume-pricing evidence where used;
- app, API, webhook, ERP, CRM, warehouse, marketplace, and accounting inventories;
- a dated source backup or export archive;
- a note describing records that can still change before the migration window.
| Evidence item | Owner | Ready condition |
|---|---|---|
| Access log | Store administrators | Required administrative areas are reachable |
| Product and inventory archive | Catalog and operations | Parent/variant records and stock evidence can be reconciled |
| Customer and Order archive | Customer operations and finance | Expected records and key fields are present |
| Content and URL inventory | Content or SEO owner | Priority pages and routes have owners and destination decisions |
| Dependency register | Technical and business owners | Every important application or external system has a continuing owner |
Prepare Products, Options, Variants, and Custom Fields
Jumpseller Product Options can generate real variants or collect Customer input, depending on the option type. Custom fields describe Products and can support filtering when represented consistently. Prepare source Product families that make these distinctions clear.
Include:
- simple Products;
- Products with size, color, material, or other variant-generating options;
- Products with variant-level SKU, stock, price, cost, weight, images, or external IDs;
- Products that collect text, longer messages, file uploads, dates, or optional extras;
- Products with custom fields used for brand, specification, compatibility, season, material, or filters;
- digital or non-stock Products;
- bundles, subscriptions, quotes, personalization, or app-controlled Products;
- Products whose inventory or Product data is maintained by an external system.
| Source behavior | Jumpseller preparation decision | Evidence to attach |
|---|---|---|
| Choice creates an independently stocked or priced item | Variant-generating option | Parent/child IDs, option values, SKU, price, stock, cost, weight, image, and external IDs |
| Buyer enters a one-time value | Text, text-area, file, or other Customer input | Storefront example and historical Order-line example |
| Optional extra does not create stock | Non-variant option or app-owned relationship | Price effect, allowed values, and Order-line evidence |
| Value describes the Product | Custom field | Field type, controlled values, filter use, and display owner |
| Logic depends on an app or external system | Application or external owner | Rule description, parent records, and durable identifiers |
Normalize option and custom-field names. Filters depend on consistent vocabulary, so “Size,” “Sizes,” and “Shoe size” should be unified only when they represent the same business concept.
Prepare Categories, Filters, Navigation, Content, and URLs
Jumpseller Categories own Product grouping and hierarchy, while navigation owns menu placement. Product filters can derive from variant-generating options and suitable custom fields. Prepare these structures separately.
| Source structure | Preparation question | Ready evidence |
|---|---|---|
| Stable Product Category | Should the hierarchy and membership remain? | Category tree and Product assignments |
| Menu branch | Which Category, page, Product, or external route should it reference? | Navigation outline |
| Brand or material filter | Should it become a controlled custom field? | Value list and filter owner |
| Size or color filter | Does it come from consistent Product Options? | Controlled option vocabulary |
| Campaign collection | Is it a temporary Category, landing page, promotion, or theme component? | Campaign owner and retain/retire decision |
| Internal classification | Does it need to remain public? | Reporting or external-system owner |
Create a content and URL inventory for Product routes, Category routes, CMS Pages, Blog Posts, policy pages, campaign pages, files, and high-value external links. Record the source path, intended Jumpseller destination, metadata, internal links, localization, and redirect need.
Jumpseller can create redirects when routes change, but migration preparation should still define which old routes matter and what destination best matches the original Customer intent.
Prepare Inventory and Commercial Relationships
Document whether stock is owned by Jumpseller, by individual variants, by inventory locations, or by an external ERP or warehouse. A total quantity is insufficient when fulfillment depends on location or a variant-level key.
Prepare:
- Product- and variant-level stock examples;
- unlimited-stock or non-stock Product examples;
- location-specific quantities where the Store will use location inventory;
- warehouse, supplier, or ERP identifiers;
- base prices, compare-at values, costs, volume pricing, and promotions;
- Customer Category and price-list relationships where used;
- active and obsolete pricing rules.
| Commercial record | Preparation evidence | Ready condition |
|---|---|---|
| Variant stock | Variant and location matrix | Every quantity has a sellable-item owner |
| Unlimited or non-stock state | Product examples | Blank, zero, and unlimited values are not confused |
| Customer-specific price | Customer Category and price-list examples | Customer and Product assignments are explicit |
| Volume price | Quantity thresholds and Product examples | Threshold and price remain connected |
| External inventory key | ERP/WMS reference list | The key is attached to the correct Product or variant |
Prepare Customers and Historical Orders
Prepare Customer examples covering registered accounts, guest buyers, multiple addresses, Customer Categories, price-list eligibility, tax or company information, marketing consent, loyalty or membership applications, and external CRM identifiers.
Prepare Orders covering:
- ordinary and variant Products;
- Customer-entered text or file inputs;
- Customer Category or special-pricing context;
- paid, pending, abandoned, canceled, refunded, and partially fulfilled states;
- discounts, taxes, shipping, multiple currencies, and manual notes;
- fulfillment and tracking references;
- marketplace, ERP, accounting, CRM, or warehouse IDs.
| Preparation item | Owner | Ready condition |
|---|---|---|
| Customer identity rules | Customer operations | Duplicate and guest-handling rules are documented |
| Customer Categories | Commercial owner | Each retained category has a defined pricing or segmentation purpose |
| Address scope | Customer operations | Account addresses and historical Order addresses are distinguished |
| Order history | Support and finance | Representative Orders explain line choices, totals, statuses, and references |
| Authentication continuity | Customer experience | Account-access and Customer communication responsibilities are defined |
Inventory Applications, APIs, and External Systems
Create a register for applications, APIs, webhooks, scripts, feeds, and external systems that create or update Jumpseller records.
Include:
- Product feeds and marketplaces;
- inventory, ERP, warehouse, and fulfillment systems;
- CRM and marketing platforms;
- loyalty, subscription, booking, bundle, quote, review, or Product-customization applications;
- tax, shipping, payment, and accounting integrations;
- analytics and consent systems;
- custom theme logic that reads Product fields or application data.
For every dependency, record the business purpose, parent records, field or table names, export availability, external IDs, future owner, and retain/replace/retire decision. The register is ready when application-owned data can be traced to its parent Product, Customer, Order, content record, or external workflow.
Select Jumpseller Representative Migration Test Samples
| Sample | Preparation purpose |
|---|---|
| Simple Product | Establish ordinary Product, Category, image, price, and stock preparation |
| Variant-heavy Product | Expose option vocabulary, variant identity, inventory, price, and images |
| Personalized Product | Expose text, file, or optional Customer input |
| Product with custom fields | Expose descriptive and filterable field ownership |
| Location-aware or externally stocked Product | Expose inventory ownership and external IDs |
| Customer in a commercial category | Expose category, pricing, address, and account context |
| Complex historical Order | Expose selected options, custom inputs, discounts, statuses, fulfillment, and references |
| Priority Category or page URL | Expose content, metadata, navigation, and redirect preparation |
| App-owned record | Expose continuing application or external-system ownership |
Attach the source ID, business reason, expected Jumpseller owner, related external IDs, and known exclusions. The sample set should cover distinct behavior rather than simply the highest-value records. Use separate samples when variants, Customer inputs, custom fields, location inventory, Customer pricing, and app-owned records cannot be represented honestly by one Product or Order.
Complete the Jumpseller Readiness Gate
| Readiness question | Required evidence | Ready condition |
|---|---|---|
| Is required access available? | Access log | Source and Jumpseller administrative areas are accessible |
| Are Product structures classified? | Product-family matrix | Variants, Customer inputs, custom fields, and app records have owners |
| Are Categories and filters normalized? | Category tree and vocabulary list | Navigation and filter sources are defined separately |
| Is inventory ownership clear? | Product/variant/location matrix | Each quantity and external key has an owner |
| Are Customers and Orders represented? | Sample ledger | Important account and historical transaction patterns are covered |
| Are priority URLs mapped? | URL inventory | Each priority route has a destination or retirement decision |
| Are dependencies owned? | Application and integration register | Every critical dependency has a continuing owner |
| Are backups and exports current? | Dated archive | Source evidence can be recovered independently |
Preparation is complete when the team can explain how each important source relationship should be represented in Jumpseller and no critical decision depends on undocumented application behavior. Any remaining uncertainty should have a named owner, a specific evidence request, and a deadline before the affected migration work is scheduled.
Conclusion
Jumpseller preparation should separate parent Products, variants, Customer inputs, custom fields, Categories, filters, inventory, Customer Categories, Orders, content, and integrations before migration. The source may store those meanings together, but the destination needs explicit ownership and consistent vocabulary.
A strong evidence package makes the representative migration test representative and gives each sample a clear owner, source expectation, and supporting record set.
Common Questions
What should be prepared first for a Jumpseller migration?
Start with the Product-family and ownership map. It determines which source values become variants, Customer inputs, custom fields, Categories, external identifiers, or application-owned records.
How should Product Options and custom fields be prepared differently?
Prepare Product Options when values create sellable variants or capture Customer choices. Prepare custom fields when values describe the Product or support filtering without creating inventory-bearing combinations.
Why must Category and navigation preparation remain separate?
Categories own Product grouping and hierarchy, while navigation owns menu placement and links. Migrating Categories does not automatically recreate the intended storefront path.
What inventory evidence is required?
Prepare Product- and variant-level quantities, unlimited-stock examples, location assignments where used, and external warehouse or ERP keys. Every quantity should have a clear owner.
Which Orders should be selected for representative migration test preparation?
Include Orders with variants, Customer-entered options, special pricing, different statuses, refunds or cancellations, fulfillment references, and external-system IDs.
When is Jumpseller preparation complete?
It is complete when access and backups are ready, Product and inventory ownership is documented, Categories and filters are normalized, Customers and Orders are represented, URLs are mapped, and every important application has a continuing owner.