Maropost Ecommerce Cloud to BigCommerce migration
Plan a Maropost Ecommerce Cloud to BigCommerce migration. Map catalogue, customer and order records, then check redirects, checkout and the store switch.
- Published
- Last updated
A Maropost Ecommerce Cloud to BigCommerce migration is possible through mapped exports and supported BigCommerce imports or application programming interfaces (APIs). Products and customer records need field mapping. Historical orders need a separate migration path, while checkout settings and connected services need rebuilding and testing.
This guide fits retailers moving a Neto by Maropost store. The main risk is preserving the visible catalogue while losing the relationships behind stock, customer accounts and past orders. Keep the source records available until the new buying and support paths pass acceptance checks.
Identify the source and target store
Identify the exact Maropost product before choosing a transfer method. Record the store’s product name, version and enabled modules. Neto export instructions must match the control panel you actually use.
In the destination, record the BigCommerce plan, storefront and product import experience. List requirements such as wholesale customer groups or multiple inventory locations against that configuration. Assign an owner to each requirement before arranging a migration service.
Maropost’s export-template documentation covers inventory, category/content, customer, order and payment exports. An exportable field still needs a supported destination field. Export availability doesn’t establish an automatic end-to-end transfer.
BigCommerce’s modern product import guide uses comma-separated values (CSV) files. It excludes creating product modifiers, assigning shared variant options and importing local image files. Identify these cases before choosing CSV as the catalogue method.
For a managed transfer, obtain a written scope naming Neto, the records included and the handling of failed rows. Specify history coverage and any exclusions. BigCommerce’s migration service information describes several transfer routes, but a general migration offer isn’t a confirmed connector for your store.
Move when the destination meets a business requirement your current setup cannot meet economically. Keep Maropost while a required warehouse or fulfilment workflow has no accepted replacement. Include overlapping subscriptions and connector work in the migration budget.
Map and preserve the business records
Create a mapping register that connects each source identifier to its destination identifier and an accountable owner. Keep an untouched export alongside every transformed import file.
For Neto customers, the customer export wizard supports configurable fields and identifies Username as a unique customer identifier. Preserve it in the mapping register even if the new account uses another identifier.
Transfer register
| Record | Transfer method | Preserve | Manual work or limit | Owner |
|---|---|---|---|---|
| Products and variants | Mapped CSV or catalogue API | Source ID, stock keeping unit (SKU), options, price and stock | Map new destination IDs. Rebuild modifiers outside the modern CSV import. | Catalogue lead |
| Images and categories | Supported catalogue fields or API | Image files, product associations and category hierarchy | Stage reachable image URLs and inspect their destination copies. Review category assignments. | Merchandising lead |
| Customers | Customer import or customer API | Source username, account details and approved address fields | Deduplicate before loading. Plan account activation or password reset without promising password portability. | Customer operations lead |
| Consent | Explicit destination mapping plus retained evidence | Consent status, source and supporting records | Keep consent distinct from account creation. Do not treat an imported account as a new opt-in. | Marketing owner |
| Historical orders | Orders API or scoped migration service | Source order number, customer link, line items and totals | Select history coverage. Map IDs before importing orders. | Migration developer |
| Refunds and payments | Retained source records, with separately scoped destination handling | Original transactions, refund references and reconciled balances | A recreated order doesn’t transfer the original payment transaction or prove it can be refunded from the new store. | Finance lead |
| Policies and content | Rebuilt pages and reviewed content transfer | Approved wording, media and old URLs | Review navigation, forms and policy links in the new storefront. | Content owner |
BigCommerce’s order preparation guide requires destination product and customer IDs for correct links. Keep source order numbers in an external-reference field instead of assuming the new platform assigns the same numbers.
For historical API orders, BigCommerce documents external_source: M-MIG to exclude them from billing calculations and prevent inventory deductions. Apply this migration marker to historical imports through the selected implementation. Don’t replay old orders as new purchases. The order migration overview explains the billing risk.
Set the history boundary explicitly. For example, a fictional retailer might import open orders and a selected period of completed orders, while retaining older records in a restricted archive. Record the excluded count and how staff will retrieve those records.
Reconcile source records against imported, deliberately archived and failed records. Keep product counts separate from variant counts. For orders, compare totals and refund balances as well as counts. A matching order count can still hide a wrong customer association.
Rebuild the customer’s buying and support path
Rebuild the complete journey in the destination before changing the public store. A customer must find the right variant, buy the available stock and receive the promised delivery option.
Use a fictional product with size and colour variants. Search for it, select one variant and add it to the basket. Confirm that the basket keeps its SKU and price. Then check delivery eligibility and the final checkout total using the payment provider’s test mode.
Assign one system as the stock source for each migration stage. Reconnect accounting and fulfilment services against the new destination IDs. Disable duplicate order processing during rehearsals so a test cannot trigger a real dispatch.
Build a URL map from old product, category and policy addresses to their specific replacements. BigCommerce documents CSV and API support for 301 redirects in its other-data transfer guide. Test that an old product link reaches the corresponding product, without a redirect loop or a detour to the homepage.
Update product references in feeds, email templates and shopping assistance. An assistant needs the new product URLs and approved policy sources. Inspect a delivery answer and follow the product link it returns.
Test an existing-order question separately. Staff must retrieve the original order using the customer’s reference, including orders kept only in the archive. Keep access restricted to authorised staff. Don’t let a product search answer stand in for a tested order-support connection.
Customer accounts also need a return path. BigCommerce’s account-management guidance describes forcing a password reset during migration. Rehearse the chosen login process and its customer message. Importing a customer row doesn’t demonstrate that an old password works.
Verify and switch the store
Approve the switch only after the rehearsal produces reconciled records and working customer journeys. Name one business decision owner who can approve the production change or hold it.
Acceptance checks
| Check | Expected result |
|---|---|
| Variant selection | Each option combination maps to the intended SKU, price and stock quantity. |
| Tax and delivery | Representative baskets match approved tax treatment and shipping rules, including restricted destinations. |
| Checkout | A provider test transaction creates one order with the correct total and confirmation. A declined payment follows the expected recovery path. |
| Refund handling | A test order follows the approved refund process. Historical refunds remain traceable to their original processor records. |
| Integrations | One accepted order reaches each intended service once, with the correct destination IDs and stock effect. |
| Customer access | The account recovery flow works and imported orders appear only for the correct customer. |
| Old URLs | Each sampled old URL reaches the intended new page. Missing destinations have an explicit decision. |
Keep rehearsal records and failures available to the decision owner. A rejected import row needs a correction and a repeat of the affected check before it counts as accepted.
Plan the production sequence in order:
- Preserve the source exports, URL map and current domain configuration. Retain access to the old store and its fulfilment tools.
- Freeze relevant record changes or define a delta import for records created or updated after the initial export. Assign ownership of orders arriving during the transition.
- Reconcile the final stock, customer and order changes. Use the mapping register to prevent duplicate creation when retrying failed records.
- Obtain the decision owner’s separate authorisation for the production switch. Record who changes the domain and enables live payment and fulfilment connections.
- After the authorised switch, reconcile new orders with payment and fulfilment records. Monitor failed checkouts and old-URL errors, then resolve each affected record.
BigCommerce’s order migration procedure describes testing before full loading and reconciling counts and relationships afterwards. Use its delta approach to identify changed records instead of rerunning the whole import blindly.
Define rollback triggers before switching, such as a blocked checkout or unexplained stock differences. Keep the previous routing configuration and source access ready. If new orders exist on BigCommerce, account for them before routing sales back to Maropost. Changing the domain alone won’t reconcile those transactions.
Give the migration provider a failure pack containing the source reference, destination ID and expected result for each unresolved record. Keep the old system or archive available until finance and customer operations accept the reconciliation and support lookup process.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.