Skip to main content
FilterIQRequest access
Menu
Type to search across all documentation
NavigateEnterOpenEscClose
3 min read

Migrate from Boost Commerce

How to switch from Boost AI Search & Discovery to FilterIQ.

Migrate from Boost Commerce

Use this guide to plan and validate a move from Boost Commerce. FilterIQ is in private preview; confirm access and the workflows your store needs before changing the live integration.

Before You Start

  1. Document your current configuration: Note your current filter setup, synonym list, and any merchandising rules in Boost
  2. Export synonyms: If you have custom synonyms in Boost, export them (if available) or note them down
  3. Screenshot your filters: Take screenshots of your current filter sidebar for reference

Migration Steps

Step 1: Install FilterIQ

Keep the current storefront and its configuration available as a rollback reference. Installation or app-setting changes can have store-wide effects, so confirm the proposed sequence with the team.

  1. Request private-preview access; if accepted, follow the installation path supplied by the team.
  2. Create a duplicate theme and record the Boost integration's settings and activation state.
  3. Review the available AI-assisted draft and check catalogue sync coverage before previewing it.

Step 2: Configure to Match Your Needs

After AI Setup:

  1. Filters: Compare the AI-generated filters to your Boost configuration. Adjust filter types, ordering, and labels to match your preferences
  2. Synonyms: Re-add your synonym pairs in Search → Synonyms
  3. Merchandising: Set up any merchandising rules you had in Boost using our presets and custom rules

Step 3: Test in Preview

  1. In the duplicate theme, disable the overlapping Boost integration and enable the supplied FilterIQ extension as agreed during onboarding.
  2. Open the preview and check search queries, filter combinations, sorting, empty results and merchandising targets.
  3. Test mobile and keyboard interactions. Confirm that changes to shared app settings have not affected the live theme.

Step 4: Go Live

  1. Record accepted test results and confirm the rollback steps.
  2. Publish the accepted theme and configuration with the intended single search/filter integration enabled.
  3. Repeat the checks on the live storefront and review available event coverage.
  4. Keep the previous configuration until you have decided the observation period is sufficient.

Step 5: Uninstall Boost

For a store with Boost installed, review any remaining features it supplies and the provider's billing/removal instructions before uninstalling through Shopify admin. Uninstalling is a separate decision from switching the storefront integration.

Feature Mapping

Current requirementFilterIQ review task
Product searchReplay representative queries and check expected matches
Product and collection filtersRecreate required sources, groups and scopes, then compare results
MerchandisingRecreate supported actions and inspect rule priority and manual product targets
AnalyticsCompare the events and reports available under the proposed plan
Recommendations, bundles or other Boost featuresIdentify each dependency and confirm a separate supported solution before removing it

What Won't Transfer

  • Historical analytics: Boost's analytics data stays with Boost
  • Custom CSS: You'll need to re-apply any custom CSS using our class names
  • Synonyms: Must be re-entered manually
  • Merchandising rules: Must be re-created using our rule system

Timeline

Estimate installation, sync, configuration review, synonym/rule recreation, testing and the observation period from your own store. Timing depends on catalogue and theme complexity; a first draft is not evidence that migration is complete.

For rollback, restore the retained theme and Boost settings, disable the FilterIQ integration in that theme, and repeat the original query/filter checks. Shared configuration may need restoration separately.

Need Help?

If you need assistance, contact us at support@filteriq.app to confirm available migration guidance and any commercial terms.

Was this page helpful?