Migrating Rules From Another App

If you’re switching to Kedra Checkout Rules from another checkout customization app, here’s how to recreate your rules and avoid common issues during migration.

Step 1: Document Your Existing Rules

Before uninstalling your old app, write down every rule you have:

• Rule type (hide, rename, reorder, discount, validation)
• Which methods it targets (exact payment or shipping method names)
• Conditions (country, cart total, customer tags, products, etc.)
• Action details (new name for renames, discount amount, error message for validation)

Tip: Take screenshots of each rule in your old app for reference.

Step 2: Create Rules in Kedra

For each rule from your old app, create the equivalent in Kedra Checkout Rules:

1. Click Create rule and select the matching rule type.
2. Enter the same conditions and settings.
3. Set status to Test first — don’t activate immediately.

Mapping Common Features

Step 3: Test Each Rule

Before uninstalling your old app:

1. Set all new Kedra rules to Test mode.
2. Go to checkout with test@testing.com.
3. Verify each rule works as expected.
4. Pay special attention to:
   • Correct payment/shipping method names
   • Conditions triggering as expected
   • Rename rules targeting the right methods

Step 4: Switch Over

Once all rules are tested:

1. Deactivate rules in your old app (or uninstall it).
2. Activate all rules in Kedra by changing status to Active.
3. Do a final live checkout test to confirm everything works.

Common Migration Issues

Rules Not Working After Migration

The most common cause is incorrect method names. Payment and shipping method names may differ between apps or may have changed since you set up the old rules.

Fix: Temporarily disable all rules, go to checkout, and note the exact method names Shopify shows. Update your rules with these exact names. See How to Find the Exact Original Method Name.

Rename Rules Affecting the Wrong Method

If your old app used partial matching (e.g., “Standard” matching “Standard” and “Standard Express”), and you migrated the same text to Kedra with “Contains string” trigger, you’ll see the same issue.

Fix: Switch to Equals to trigger and use the full exact method name.

Conditions Not Matching

Different apps may implement conditions differently. For example:

• Some apps check “cart total” as subtotal, others as the total including tax.
• Product conditions may work differently (single product vs entire cart).

Fix: Test each condition carefully. Use Kedra’s Test mode to verify without affecting real customers. See How Conditions Work.

Running Both Apps at Once

While migrating, you may temporarily have both apps active. This can cause conflicts — for example, both apps trying to hide the same method, or rename rules from one app interfering with the other.

Fix: Keep new Kedra rules in Test mode until you deactivate or uninstall the old app. Only activate Kedra rules after the old app’s rules are disabled.

Need Help?

If you’re having trouble migrating rules, reach out to us through the in-app chat or email us at info@kedra.io. We can help you set up your rules to match your previous configuration.

Related

• Creating Your First Rule
• How to Find the Exact Original Method Name
• My Rule Isn’t Working — Checklist