When migrating from DeliveryCheckout to the new nShift Checkout, your configurations need to be recreated in nShift Checkout. There are two ways to do this:
| Option 1: Import existing configuration(s) | Option 2: Set up from scratch |
|---|---|
| Import your DeliveryCheckout (v1) configuration from a JSON file to get started quickly. | Create a new configuration in nShift Checkout for full control and to fully leverage new capabilities. |
|
Best for:
|
Best for:
|
|
Recommendation Use the migration as an opportunity to review and improve your setup. Even if you start with an import, consider refining or rebuilding parts of it to fully benefit from nShift Checkout's capabilities. |
Option 1: Import existing configuration(s)
Import your DeliveryCheckout (v1) configuration using a JSON file to get started quickly. This is a good starting point, but there are some important things to be aware of before and after the import.
Read more: Exporting and importing configurations
Things to be aware of
- There are structural differences between v1 and v2 (for example, Conditions vs the new Rule Engine)
- Imported configurations will often require adjustments after import
- Most suitable for less complex configurations
- Condition lists and agent lists are not included in the import and need to be moved separately
Option 2: Set up from scratch
Create new configurations in nShift Checkout for full control and to fully leverage new capabilities. This approach results in a cleaner, more maintainable setup and is recommended for more complex configurations.
Read more: Setting up nShift Checkout configurations
Examples of improvements when building from scratch
A fresh start
Building from scratch is the perfect opportunity to step back and rethink your checkout setup from the ground up. Rather than replicating what existed in DeliveryCheckout, you can fully leverage the capabilities of nShift Checkout and design the optimal delivery experience for each scenario, whether that is based on cart contents, market, product type, or customer segment.
New rule engine
Imported legacy conditions are automatically converted into rules, but rebuilding them directly in the new rule engine often results in better performance, improved readability, and easier maintenance.
Easier market-specific setups
With the new Groups functionality, you can create and maintain separate configurations per market instead of managing one large, complex configuration.