Prepare Custom Migration Requirements
Turn non-standard requirements into quote-ready technical scope by separating supported configuration from bespoke logic, data structures, third-party dependencies, and custom platform behavior.
Prepare Custom Migration Requirements
Section titled “Prepare Custom Migration Requirements”Use Custom Migration when standard configuration and available Standard Add-ons cannot produce the required result. See What Custom Migration Handles for scope examples.
Custom Migration covers unsupported data, third-party app, plugin or module data, bespoke logic, non-standard relationships, schema engineering, external-system handling and other agreed work beyond Standard scope. It is also required for CSV, XLS or XML Sources and for Source or Target Platforms outside the standard supported directory.
An Upgrade from Standard Migration or Managed Migration to Custom Migration must include mutually agreed, documented technical work. This can include tailored configuration, schema adjustments, business rules, unsupported platform handling or other bespoke development.
How Custom Migration scope becomes part of the purchased service
Section titled “How Custom Migration scope becomes part of the purchased service”Describe the scenario, requirements, constraints, expected result and available access or data. Next-Cart reviews technical feasibility and works with you to agree on the scope.
A requirement becomes part of the purchased service when it is documented and accepted through the Checkout purchase, approved quote, written scope or another accepted order confirmation. Later material changes may require a revised feasibility review, scope, fee, capacity, Add-on selection, responsibility split or delivery timing before additional work begins.
File-based sources and Custom Platforms
Section titled “File-based sources and Custom Platforms”CSV, XLS, and XML
Section titled “CSV, XLS, and XML”CSV, XLS, and XML are file-based Source Platform selections handled through Custom Migration. Their included file workflow migrates Products only. Follow the matching CSV, XLS, or XML Product file guide for the Product input.
If the project also requires Customers, Orders, another entity type, non-standard relationships, or special business logic, describe each additional requirement in the Custom Migration request. Those requirements are assessed and developed for the individual migration rather than assumed to be supported by an extra file. File-based projects follow the same Custom Migration scope-agreement, quote, and purchase workflow as other Custom Migration projects.
Example: CSV to Shopify with additional scope
Section titled “Example: CSV to Shopify with additional scope”A CSV → Shopify project uses the CSV Source Platform and the Shopify Target Platform. The included CSV file workflow migrates Products. If the project must also migrate Customers, Orders, or apply project-specific business logic, add those requirements to Custom Requirements so Next-Cart can scope and develop the additional handling. The project follows the same Custom Migration scope-agreement, quote, and purchase workflow as any other Custom Migration request.
Because CSV has no Source Store URL, the Shopify Target URL becomes locked when the successfully connected CSV-to-Shopify setup proceeds to the Configuration step. Review Store URL Locking and Store Identity before selecting Continue to Configuration.
Platform not present in the supported directory
Section titled “Platform not present in the supported directory”A Source or Target Platform that is not present in Next-Cart’s standard supported directory is handled as a Custom Platform project. Define the platform, available source access, data structures, data conversion requirements, relationships, expected Target result, and validation criteria. Next-Cart then scopes the technical extraction and migration approach for that project.
Select CSV, XLS, or XML when the project is intentionally based on that Product file workflow. If the project instead depends on platform-specific extraction, conversion, or broader source data from an unlisted platform, define the actual platform and requirements as Custom scope.
Alternate connection methods within Custom Migration
Section titled “Alternate connection methods within Custom Migration”A Custom Migration project can use an alternate connection method that differs from the platform’s standard Connect Stores setup when the customer and Next-Cart agree on that method after the requirements, constraints, and technical feasibility are discussed. This does not change the standard supported-platform directory and does not make the alternate method available by default.
For example, EKM uses File Upload as its standard Source connection method. If the mutually agreed Custom Migration scope specifically uses EKM API access, authorize that connection through EKM API Connection. Projects without that API scope should continue to use EKM Source Data Export and the normal File Upload workflow.
When an alternate connection method is required, include the platform, access method, required credentials or authorization, data scope, implementation dependencies, and validation criteria in the Custom Migration requirement.
Before you prepare a Custom Migration requirement
Section titled “Before you prepare a Custom Migration requirement”Confirm whether the requirement is covered by one of these paths:
| Capability | Use it when | Custom Migration threshold |
|---|---|---|
| Standard data selection | You need to include supported data types. | The required data is not exposed as a supported data type or supported source record set. |
| Additional Options | You need supported target-data clearing, name cleanup, description-image handling, identifier preservation, or SEO URL behavior. | The required behavior exceeds the option shown for the migration configuration. |
| Attribute Mapping | You need supported Language, Customer Group, or Order Status mapping. | The target value or mapping behavior cannot be represented through the standard mapping control. |
| Data Filter | You need field-level conditions per data type to control which records migrate. | Required fields, operators, logic, relationships, or external data are unavailable. |
| Data Transformation | You need a supported value change on retained records before mapping. | The required operator is unavailable, or the requested value handling depends on external data or bespoke/multi-record logic beyond Standard Add-ons. |
| Advanced Data Mapping | You need to redirect a supported source or transformed value to a different compatible target field without changing it again as part of mapping. | The required field or destination is unsupported, value compatibility cannot be satisfied, or the requirement needs non-standard behavior. |
| Advanced Database Mapping | You need supported source or transformed value/database-column mapping, the selected Source setup supports Advanced Database Mapping, and the Target Platform is supported as a database-mapping destination. | The selected Source setup or Target Platform is unsupported, the field/column or destination is unavailable, value compatibility cannot be satisfied, or bespoke schema behavior is required. |
Assess Data Update for supported existing-record field refreshes. Unsupported update fields, transformations, destinations, or arbitrary matching need separate scope review.
Choose the Custom Migration operation mode
Section titled “Choose the Custom Migration operation mode”For a new Custom Migration purchase, choose who will run the migration.
| Operation mode | What to plan for |
|---|---|
| Self-Execute | The customer operates the migration through the Dashboard after the approved Customization is prepared and verified. Define enough requirements and pass conditions to verify the tailored behavior before execution. |
| Expert Handle | Next-Cart engineers manage and execute the agreed migration work. Include scheduling, access, dependencies, and execution expectations in the scope. The additional engineering fee is included in the final itemized quote. |
Both modes retain Dashboard visibility and operational access to inspect, manage and use the available execution controls. With Expert Handle, keep customer-initiated execution aligned with the agreed schedule because Next-Cart is responsible for the agreed work.
Requirements that usually need Custom Migration
Section titled “Requirements that usually need Custom Migration”- data stored in third-party apps, plugins, modules, or extensions;
- custom fields whose required handling remains outside supported Advanced Data Mapping or Advanced Database Mapping scope;
- database tables or columns that remain unsupported after Advanced Database Mapping eligibility and support are checked;
- tailored or bespoke Add-on behavior that modifies or exceeds a Standard Add-on;
- multi-record or bespoke conditional processing outside supported Data Transformation;
- bespoke relationship reconstruction;
- unsupported filter logic;
- custom platform extraction or target handling;
- data from external systems such as ERP, CRM, marketplace, subscription, or loyalty services;
- target output requiring custom code, custom storage, or non-standard placement.
Extension, app, module, and plugin data
Section titled “Extension, app, module, and plugin data”Application-owned data can create three different Custom Migration questions: extracting non-standard data from a Source Store, loading data into a Target Store application, or isolating custom structures inside an otherwise supported Source Platform. Keep those directions separate because they require different evidence, access, and acceptance criteria.
Source extension, app, module, and plugin data
Section titled “Source extension, app, module, and plugin data”Treat source application-owned data as a separate migration requirement. Selecting a related standard data type does not automatically include extension tables, plugin metadata, application API objects, custom post types, module records, or the relationships that make those records meaningful.
For each source extension or application, record:
- the extension/application name and business purpose;
- the authoritative records, fields, tables, API objects, or files it owns;
- the Product, Customer, Order, Category, or other records those values belong to;
- whether the data is authoritative, derived, cached, historical, or no longer needed;
- how the source data can be accessed through the approved connection;
- the required Target Store meaning and validation evidence.
Do not request migration of an entire extension database simply because it exists. Scope the business-critical data and relationships that must survive.
Target extension, app, module, and plugin data
Section titled “Target extension, app, module, and plugin data”A Target Store extension creates a different problem: the migration must write the accepted data into a structure the target application can actually consume. Installing a target plugin or application is not equivalent to migrating its data, and moving source values into generic custom fields does not prove that the target application will recognize them.
Document the target application, the records or fields it expects, its import or API capability where applicable, and the exact target behavior that should result. Separate data migration from application installation, configuration, licensing, theme integration, or custom development unless those activities are explicitly included in the accepted scope.
Customized Source Stores
Section titled “Customized Source Stores”A customized Source Store can contain core records alongside custom fields, custom tables, modified database relationships, bespoke scripts, theme-owned data, and extension-owned logic. Do not treat the whole Store as Custom Migration automatically. First separate the parts already supported by the standard migration path or an applicable Add-on from the parts that genuinely require tailored extraction, transformation, relationship reconstruction, or target placement.
Provide representative records and expected outcomes for each non-standard requirement. A Demo Migration can reveal whether the supported path already exposes the required data, but a successful connection alone does not prove that custom structures are included.
WooCommerce Subscriptions
Section titled “WooCommerce Subscriptions”Next-Cart can use Custom Migration to transfer subscriptions from WooCommerce to WooCommerce and from other supported custom sources, including Easy Digital Downloads to WooCommerce.
Migrated subscriptions do not auto-renew on the new website in the approved workflow because renewal authorization depends on the new domain and secure payment details. After the new site goes live, Customers must log in and re-enter their payment information to enable automatic renewal for the migrated subscriptions.
Define the subscription Product relationship, Customer, subscription status, billing schedule, renewal state, recurring totals, external subscription identifiers, and the system that owns future renewals. Validate representative active and paused/cancelled subscriptions plus a renewal scenario against the target subscription system before considering the requirement complete.
WooCommerce Product attachments and downloadable content
Section titled “WooCommerce Product attachments and downloadable content”Two approved Custom Migration methods can migrate Product attachments to WooCommerce and expose them on the Product page:
- Upload and link through the Product description. Upload the attachment files to the WooCommerce website, then tailor the migration so the attachment URLs are written into the Product description. The resulting links are displayed through the Product description on the Product page.
- Use a Product Attachments plugin. Install the target Product Attachments plugin, then tailor the migration so attachments are imported according to the data structure used by that plugin.
For either method, identify where each file is stored, which Product or variation owns it, whether it is public or protected, and which target feature will display or deliver it. Validate file accessibility, Product association, Customer entitlement where applicable, and target storefront/admin presentation separately.
WooCommerce wholesale pricing
Section titled “WooCommerce wholesale pricing”Wholesale pricing is not a native WooCommerce feature in the approved migration workflow, so install a WooCommerce wholesale plugin before expecting migrated wholesale prices to be represented. After the target wholesale structure is available, Custom Migration can tailor the migration so Product wholesale prices are written to the WooCommerce store.
Target plugin examples used by the approved workflow include:
- WooCommerce Wholesale Prices & B2B Plugin;
- Ultimate WooCommerce Wholesale and B2B Solution;
- Wholesale For WooCommerce.
These examples do not imply that every wholesale extension uses the same database structure. Install and configure the chosen target extension first, then provide its field/role/pricing model so the migration can write wholesale values into the correct extension-owned structure.
Also document the source plugin or pricing owner, Customer roles or groups, quantity tiers, tax treatment, visibility rules, currencies, catalogs, and other conditions that determine who receives the wholesale value. Validate representative wholesale and retail Customers and the rules that control each price.
WooCommerce abandoned carts
Section titled “WooCommerce abandoned carts”If Customer cart data is stored in the Source Store database or can be retrieved through the Source Platform API, Custom Migration can tailor the migration to transfer those carts to WooCommerce.
After migration, Customers can see their previous carts after signing in to the new WooCommerce site. To view abandoned carts in WooCommerce admin, install the WooCommerce Abandoned Cart plugin.
Define the Source Store cart structure, Customer or session identity, Products/variations and quantities, and the WooCommerce cart or recovery behavior that must be preserved. Validate both the signed-in Customer cart result and the required administrative view.
WooCommerce bundle, composite, and custom-option Products
Section titled “WooCommerce bundle, composite, and custom-option Products”For source Products with custom options, the approved default WooCommerce conversion maps the custom options to WooCommerce variations when the option types are drop-down, check-box, select box, or radio button.
When a Product has more than 4 custom options or uses option types outside that default list, one supported alternative is the WooCommerce Extra Product Options plugin. The approved workflow identifies support for option structures including check-box, radio button, select box, swatches, textarea, input box, upload, date, range picker, color picker, product elements, and additional option types. If this plugin model is selected, use Custom Migration so the migration writes the Product options into the plugin-owned target structure.
Other selling models can require WooCommerce Product Bundles, Composite Products, Product Add-Ons, or another extension-owned structure. For composite-product workflows, established target options include WooCommerce Composite Products and WPC Composite Products for WooCommerce. Define the selling behavior that must be preserved, required/optional choices, pricing or quantity rules, dependency rules, and representative Products that prove the result. Validate the migrated Product in both Admin and the storefront.
Shopify metafields and storefront output
Section titled “Shopify metafields and storefront output”Shopify metafields can be migrated as data for Products, variants, collections, and other supported resources. Migrating the value and displaying it on the storefront are separate tasks.
For a Shopify 2.0 theme that supports metafield dynamic sources, use the following storefront-display workflow:
- In Shopify admin, open Online Store > Themes.
- In the active theme section, select Customize. Another theme in the Theme library can also be customized when that is the intended storefront theme.
- In the top dropdown, select Products, then choose the Product template in use.
- In Product information, select Add block, then select Text.
- Add each metafield to the new text block with Connect dynamic source.
If the theme does not expose the required metafield presentation, the approved technical fallback is theme-code rendering:
- Open Online Store > Themes.
- For the active theme, select Actions (…) > Edit code.
- Locate
product.liquid. Depending on the theme, the file can appear under Templates, Sections, or Snippets. - At the required Product-page position, insert the storefront markup. The approved example reads the
global.height,global.width, andglobal.depthProduct metafields:
<div class="additional-attributes"><table><tbody><tr><th>Height</th><td>{{ product.metafields.global.height }}</td></tr><tr><th>Width</th><td>{{ product.metafields.global.width }}</td></tr><tr><th>Depth</th><td>{{ product.metafields.global.depth }}</td></tr></tbody></table></div>- Save the theme change and verify that the metafields display on the intended Product page.
The migration can preserve supported Shopify metafield data by default where the migration path exposes it. Theme editing and storefront UI implementation are separate from data migration scope, so plan the required storefront-development work with the appropriate store-development resource rather than assuming migration-service execution includes theme changes.
Shopify Gift Cards
Section titled “Shopify Gift Cards”Shopify Gift Cards can be migrated through approved Custom Migration handling even though Gift Cards are not exposed as a standard Shopify API migration entity in the documented workflow. The tailored migration imports the Gift Cards into Shopify and preserves their association with the respective Customers. When a Gift Card was created by an Order, the migrated Gift Card is also associated with the respective Order.
Define the required Gift Card source fields, Customer and Order relationships, balance or historical state that must be preserved, and representative validation records before the Custom Migration scope is mutually agreed and documented.
Full-site replication
Section titled “Full-site replication”A data migration is not a full clone of a Source Store. Themes, page layout, application behavior, checkout logic, payment configuration, shipping logic, storefront navigation, external integrations, and other operational behavior may require separate setup or Custom Migration work.
If the objective is to reproduce the complete business experience, split the requirement into explicit data, application, URL, storefront, and integration outcomes and scope each non-standard portion separately.
Prepare the requirement
Section titled “Prepare the requirement”-
Name the requirement
Use one clear name for one requirement.
-
Identify the affected data type
State whether the requirement affects Products, Categories, Customers, Orders, Reviews, Coupons, Pages, or another data area.
-
Identify the source location
Provide the field name, export column, table, metafield, app area, plugin table, module, API property, or admin location.
-
Describe the target result
State where the data should appear and what the user should be able to see, search, edit, or validate.
-
Write the logic as a testable rule
Use an if/then statement where possible. Include fallback behavior.
-
Provide representative examples
Include at least three normal examples and three edge cases where the data allows it.
-
List dependencies
Identify required credentials, exports, permissions, apps, plugins, modules, custom fields, or target settings.
-
Define pass conditions
State which records and fields must match, what differences are acceptable, and what would block sign-off.
-
Choose the correct submission path
For a new Custom Migration purchase, enter the requirement in Checkout → Custom Requirements, add supporting attachments, and select Request a Quote. For an existing migration, use the supported Custom Migration upgrade or scope-review path. Keep follow-up clarification and evidence in the order or support thread Next-Cart provides for that request.
Requirement template
Section titled “Requirement template”| Field | What to provide |
|---|---|
| Requirement name | Short, unique name. |
| Affected data type | Data area affected. |
| Source location | Field, table, export, app, plugin, module, API property, or admin location. |
| Target destination | Native field, custom field, note, tag, table, reference, or target behavior. |
| Logic | Testable rule, including conditions and fallback behavior. |
| Normal examples | Representative source records and expected outputs. |
| Edge cases | Complex, empty, duplicate, unusual, or risky records. |
| Dependencies | Access, permissions, exports, integrations, target settings, or applications. |
| Validation | Samples, pass conditions, acceptable differences, and blockers. |
Example requirement
Section titled “Example requirement”Requirement: Merge an external ERP reference into a project-specific Product relationshipAffected data type: ProductsSource location: ERP API data that is not part of the supported migration sourceTarget destination: Agreed project-specific target relationshipRule: Match the ERP reference to the migrated Product by the approved identifier and create the agreed target relationship only when the source match is unique.Validation: Check normal Products, a missing ERP reference, a duplicate ERP reference, and a Product whose source identifier changed.Assessment, quote, and purchase
Section titled “Assessment, quote, and purchase”For a new Custom Migration purchase, Request a Quote creates a Draft order. Next-Cart assesses the submitted requirements and itemizes each approved custom modification so its functional scope and price can be reviewed separately. The customer and Next-Cart then align the technical rules, execution responsibility, dependencies, and expected timeline.
After the finalized quote and order configuration are approved, the Draft moves to Pending Payment. Complete the payment workflow only when the itemized scope matches the agreed requirements. After the order becomes Paid, approved Customization is prepared and verified; an automated readiness email confirms when the project is configured for execution.
For an existing migration, approved new custom scope follows the supported Upgrade path. Use Purchase a Migration Upgrade to open the project from Statistics → View Upgrade Options and configure the supported upward change. Use Orders for differential billing, supported upgrade direction, and how a successful custom-work Upgrade is integrated into the existing migration.
Expected result
Section titled “Expected result”A complete Custom Migration requirement should make it possible to determine:
- what data or behavior is required;
- why standard configuration and purchased Add-ons are insufficient;
- where the source data exists;
- what the target result must be;
- which dependencies affect implementation;
- how the result will be validated.
Verify the requirement
Section titled “Verify the requirement”| Check | Pass condition |
|---|---|
| Capability boundary | The requirement is not already covered by standard configuration or a purchased Add-on. |
| Source evidence | Field names, locations, records, screenshots, or exports are provided. |
| Target expectation | The expected target result is specific and testable. |
| Examples | Normal and edge-case records are included. |
| Dependencies | Required access, applications, permissions, and target preparation are listed. |
| Validation | Pass conditions and blockers are defined. |
Failure handling
Section titled “Failure handling”| Issue | What to do |
|---|---|
| The source location is unknown | Ask the source store owner, developer, or app provider to identify the field, table, export, or API property. |
| The target destination does not exist | Prepare the required target field or define an approved fallback. |
| The requirement is too broad | Split it into separate testable requirements. |
| Examples are unavailable | Collect representative records before requesting implementation. |
| The requirement may be covered by an Add-on | Check Standard Add-ons first. For Advanced Database Mapping, confirm platform eligibility and schema support before escalating. |
| The result cannot be validated | Define concrete sample records and pass conditions before implementation begins. |
Direct database files and database engines
Section titled “Direct database files and database engines”Direct database migration is handled through Custom Migration rather than a generic SQL Source Platform selector. The approved technical capability includes migration from and to the following database engines when the project scope is qualified:
- MySQL;
- MariaDB;
- PostgreSQL;
- SQLite;
- MongoDB;
- Microsoft SQL (MSSQL);
- Oracle;
- IBM Db2.
Other database types can be assessed upon request.
For Microsoft SQL Server, the approved database-file workflow accepts .bak and .sql inputs. Provide the database file and describe the required business entities and Target result so Next-Cart can analyze the source structure and prepare the tailored migration handling.
PostgreSQL migration is also supported through qualified Custom Migration scope for direct database work. Because generic SQL is not a standard Source Platform selection, describe the PostgreSQL source or target, access method, schemas/tables, relationships, and required Target outcome in the Custom Migration requirement or Support Ticket rather than looking for a generic PostgreSQL/SQL switch in the Connect Stores step.
For any database-backed requirement, provide the database engine and version, access method, relevant schemas or tables, stable identifiers and relationships, representative field types, expected target outcomes, and transformation rules. Do not select a different platform merely because it uses the same database technology.
Next Steps
Section titled “Next Steps”For a new Custom Migration purchase, continue to Purchase a Migration, enter the prepared requirements and attachments, choose the operation mode, and select Request a Quote. For a changed requirement on an existing migration, use Purchase a Migration Upgrade after the Custom requirement is sufficiently defined, or use Custom Migration Escalation when the scope still requires review.