DEV Community: webdev

JSONPath — How to Query and Filter JSON Data

Deepak Kumar — Mon, 24 Aug 2026 07:32:33 +0000

JSONPath is a query language for JSON, providing the same kind of document-navigation power that XPath gives XML developers. Instead of writing nested loops or chained property accesses, you write a compact expression that pinpoints exactly the data you need — whether it lives three levels deep or is scattered across a hundred-element array.

What Is JSONPath and Why Does It Matter?

Stefan Goessner introduced JSONPath in 2007 as a direct analog to XPath 1.0 for XML. Just as XPath lets you write //book[@price<10] to pluck cheap books out of an XML document tree, JSONPath lets you write $.store.book[?(@.price < 10)] to do the same against a JSON structure.

The practical value is highest when working with API responses you don't fully control. Rather than parsing the entire payload and walking the object graph yourself, you hand a JSONPath expression to a library and get back exactly the nodes you care about. This approach is used by REST-testing frameworks like REST Assured in Java, by AWS's query language JMESPath in the AWS CLI, and by the widely used jq command-line tool (which has its own syntax but borrows heavily from the same ideas).

The Root Operator and Basic Navigation

Every JSONPath expression starts with $, representing the root of the document. From there you navigate using dot notation or bracket notation.

$.store.book.title

This reads as: "start at root, enter store, then book, then title." Bracket notation is required when a key contains a hyphen, space, or starts with a digit:

$['store']['book']['title']
$['content-type']

Sample document used throughout this article:

{
  "store": {
    "book": [
      { "title": "Sayings of the Century", "author": "Nigel Rees",     "price": 8.95  },
      { "title": "Sword of Honour",        "author": "Evelyn Waugh",   "price": 12.99 },
      { "title": "Moby Dick",              "author": "Herman Melville","price": 8.99  },
      { "title": "The Lord of the Rings",  "author": "J.R.R. Tolkien", "price": 22.99 }
    ],
    "bicycle": { "color": "red", "price": 19.95 }
  }
}

$.store.bicycle.color returns "red". $.store.book[0].title returns "Sayings of the Century".

Wildcards and Recursive Descent

The wildcard * matches all properties or elements at the current level:

$.store.book[*].author
// ["Nigel Rees", "Evelyn Waugh", "Herman Melville", "J.R.R. Tolkien"]

The recursive descent operator .. searches at any depth, not just the current level:

$..author

This finds every author field anywhere in the document tree, regardless of nesting depth — invaluable when you don't know the exact structure of a deeply nested API response but do know the key name. It can also be combined with a wildcard or index, e.g. $..[0] returns the first element of every array found anywhere in the document.

Array Slicing and Index Access

JSONPath supports Python-style array slicing:

$.store.book[0]      /* first book */
$.store.book[-1]     /* last book (negative index) */
$.store.book[0,2]    /* first and third books (union) */
$.store.book[0:2]    /* first two books (slice, exclusive end) */
$.store.book[1:3]    /* second and third books */
$.store.book[*]      /* all books */

The slice [start:end] follows Python convention — start is inclusive, end is exclusive. Negative indices count from the end, so [-1] always gives the last element regardless of array length — cleaner than computing array.length - 1 in application code.

Filter Expressions

Filter expressions select array elements matching a condition, using [?( expression )] where @ refers to the current element:

/* books costing less than $10 */
$.store.book[?(@.price < 10)]

/* books that have an isbn property */
$.store.book[?(@.isbn)]

/* books priced between $8 and $13 */
$.store.book[?(@.price >= 8 && @.price <= 13)]

Filters are evaluated per element — @ is bound to each array element in turn, and only elements where the expression is true are included. The first example above returns the two books priced at $8.95 and $8.99.

A more real-world example — extracting users whose email domain is gmail.com:

$.users[?(@.email =~ /.*@gmail\.com$/)]

Note that regex support (=~) is available in some implementations (notably the Jayway Java library) but isn't part of the original Goessner spec — check your library's docs for which operators are supported.

Built-in Functions

RFC 9535 (the JSONPath 2.0 spec, published 2024) formalizes a set of built-in functions:

$.store.book.length()          /* number of books */
$.store.keys()                 /* all keys of the store object */
$.store.book[*].price.min()    /* minimum price across all books */
$.store.book[*].price.max()    /* maximum price */
$.users[?( match(@.name, "A.*") )]   /* string matching */

length() is especially useful inside filters: $.users[?( length(@.tags) > 2 )] returns only users with more than two tags. RFC 9535's match() and search() functions use I-Regexp patterns — match() requires a full-string match, search() succeeds if the pattern matches anywhere in the string.

Practical Examples

Extract all email addresses from a user list:

{
  "users": [
    { "id": 1, "name": "Alice", "email": "alice@example.com" },
    { "id": 2, "name": "Bob",   "email": "bob@example.com"   },
    { "id": 3, "name": "Carol", "email": "carol@example.com" }
  ]
}

$.users[*].email
// ["alice@example.com", "bob@example.com", "carol@example.com"]

Find all books under $15:

$.store.book[?(@.price < 15)]
// Returns the three objects priced 8.95, 12.99, and 8.99

Get the last element when array length is unknown:

$.store.book[-1]
// Returns the Lord of the Rings object

Where JSONPath Is Used in Practice

REST Assured (Java) ships with built-in JSONPath support for API test assertions:

given().when().get("/books").then().body("store.book[0].title", equalTo("Sayings of the Century"));

JMESPath is AWS's answer to JSONPath, used by the AWS CLI's --query flag. The syntax differs (no $ root), but the concept is identical:

aws ec2 describe-instances --query "Reservations[*].Instances[?State.Name=='running'].InstanceId"

jq is the de facto standard for JSON processing on the command line. It has its own richer syntax, but many core ideas — .foo for property access, .[] for iteration, select() for filtering — map directly onto JSONPath concepts. Once you know JSONPath, picking up jq is straightforward.

JSONPath vs. JavaScript Dot-Notation Chaining

In JavaScript, plain property access (data.store.book[0].title) works fine for deterministic paths, but has real limits: if any intermediate property is undefined, the expression throws a TypeError. You need optional chaining (data?.store?.book?.[0]?.title) to be safe, and there's no built-in way to express "all elements" or "any depth."

JSONPath handles both cases with a single expression, and returns an array of matches (zero, one, or many) — which maps naturally onto scenarios expecting multiple results. For simple, known-path access, plain JS dot notation is fine. For flexible querying, filtering, and deep searches across variable-shaped data, a proper JSONPath library is the better tool.

Summary

The core operators to know: $ (root), . and [] (navigation), * (wildcard), .. (recursive descent), array slices ([0] / [-1] / [0:3]), and filter expressions ([?(@.price < 10)]). These seven cover the vast majority of real-world data-extraction tasks — for testing APIs, querying cloud resources, or processing large JSON payloads on the command line.

Want to test JSONPath expressions on your own data? JSON Formatter Hub lets you paste JSON and explore the structure interactively, entirely in your browser.

Top 10 Best BigCommerce to WooCommerce Migration Companies

Oliver Pitts — Mon, 24 Aug 2026 07:32:32 +0000

You've got a BigCommerce store but you're trapped in expensive hosting and limited by their API constraints. Time to migrate to WooCommerce. Let's talk about which companies actually understand the technical side and won't corrupt your data, break your checkout, or lose your revenue.

What Actually Happens When You Migrate BigCommerce to WooCommerce

Here's the real technical challenge with BigCommerce to WooCommerce migration.

BigCommerce is built on their proprietary platform. It's powerful. Really powerful. You can build sophisticated ecommerce systems on it. You can handle thousands of products. You can manage complex inventory. You can process high transaction volumes. It's enterprise-level ecommerce.

But here's the problem. BigCommerce is expensive. Really expensive. Your hosting starts at $29.95 per month but realistically you're paying $99 to $299 depending on sales volume. Then you're paying transaction fees. Then you're dealing with platform limitations. You want to customize something. BigCommerce either doesn't support it or you need to buy an expensive third-party app. You're trapped in their ecosystem.

WooCommerce is different. It's built on WordPress. It's open source. It's affordable. Your hosting cost is usually $10 to $50 per month. No transaction fees. No hidden platform fees. You install what you need. You pay for what you use. That's it.

But here's the technical challenge. BigCommerce and WooCommerce have completely different architectures. BigCommerce uses their proprietary database model. WooCommerce uses WordPress posts and post meta. Product storage is different. Variant handling is different. Order management is structured differently. You can't just export and import.

Migration requires:

Understanding BigCommerce's proprietary data structure
Exporting data from BigCommerce's closed system properly
Transforming data to WordPress format
Handling product variants and options correctly
Recreating product configurations
Migrating custom fields and metadata
Managing third-party applications
Setting up payment gateway integrations
Configuring shipping systems
Migrating customer accounts securely
Transferring order history with integrity
Implementing proper redirects for SEO
Testing everything thoroughly

One wrong step and you lose products. Or corrupt your product configurations. Or break customer relationships. That's serious.

A lot of companies say they can do this. Some of them actually understand the technical depth. Some of them kind of attempt it. Some of them create technical debt that causes problems for months.

The good ones understand BigCommerce's proprietary architecture deeply. They understand WooCommerce's structure. They plan migrations properly. They test thoroughly. They execute cleanly. They provide support after launch.

That's what this guide is about. Finding those companies.

Why This Matters For Developers Right Now

Database architecture complexity. BigCommerce and WooCommerce have completely different database models. BigCommerce uses a proprietary structure. WooCommerce uses posts and post meta. Schema transformation is not trivial.

Variant system differences. BigCommerce handles product variants differently than WooCommerce. Recreating variant hierarchies and options requires understanding both systems deeply.

Third-party application ecosystem. BigCommerce third-party apps are custom built. They don't transfer to WooCommerce. You need to find plugin equivalents or rebuild functionality. This is complex work.

Payment gateway integration. BigCommerce payment integrations don't transfer. You need to reconfigure in WooCommerce. Each payment gateway has different API requirements. Testing is critical.

Custom field handling. BigCommerce has custom fields for products, customers, orders. WooCommerce uses post meta. Mapping custom fields requires careful planning and data type conversion.

Performance implications. BigCommerce performance characteristics are different from WordPress. Migration gives you a chance to improve performance through proper indexing and optimization.

Developer ecosystem differences. BigCommerce has smaller developer community. WooCommerce has millions of developers. This affects how future development happens.

Scaling and maintainability. BigCommerce is often built without scalability in mind. WooCommerce is designed for scale. Migration improves long-term maintainability and reduces technical debt.

Top 10 Companies That Handle BigCommerce to WooCommerce Migrations

1. EbizON

They've handled 500+ BigCommerce to WooCommerce migrations. They understand BigCommerce's proprietary architecture and WooCommerce internals deeply.

Cost: Around $25-$99 per hour | Minimum Price: $2,000 or more

EbizON specializes in proprietary platform ecommerce system migrations. They do this constantly. They work with BigCommerce databases regularly. They know BigCommerce inside and out. They understand WooCommerce architecture completely.

Here's what they do technically:

BigCommerce system analysis: They review your complete BigCommerce installation. They understand your data architecture. They identify third-party applications. They see your product configurations. They understand your complete system.

Database schema mapping: BigCommerce uses a proprietary database schema with specific structures. They understand it completely. They map BigCommerce tables to WooCommerce structures. They understand relationships between products, variants, options, and custom data.

Data extraction pipeline: They export product data from BigCommerce efficiently. They handle thousands or millions of products. They handle complex product variants and configurations. They handle custom fields. They verify completeness. They don't lose a single record.

Transformation logic: BigCommerce data doesn't fit WooCommerce format directly. They write sophisticated transformation scripts. They handle field mapping. They convert data types properly. Text becomes post meta with proper formatting. Numbers get correct data types. Dates convert to proper timestamps. Complex objects serialize correctly.

WooCommerce database design: They design proper WooCommerce structure. Product post types optimized. Product variants properly configured. Product meta fields indexed. They don't just use defaults. They optimize for query performance and scalability.

Variant system recreation: WooCommerce uses variants differently than BigCommerce. They set up variants properly. They map BigCommerce product options. They configure variations. They handle complex variant relationships. They recreate option hierarchies.

Customer database migration: They migrate BigCommerce customers to WordPress users. They handle password hashing properly. BigCommerce and WordPress hash differently using different algorithms. They rehash passwords securely. Customer metadata transfers. Customer data is preserved completely. Customer preferences transfer.

Order history preservation: BigCommerce orders are complex with multiple related records. Order data. Order items with individual metadata. Order metadata. Customer information. Payment information. All transfer to WooCommerce. Customers can view past orders immediately. Order integrity is maintained perfectly.

Application evaluation and replacement: BigCommerce third-party applications are critical for functionality. They identify which applications are critical to your business. They find WooCommerce plugin equivalents. Some applications have direct replacements. Some need custom solutions. They evaluate compatibility. Application functionality recreates properly.

Payment gateway setup: They understand BigCommerce payment integrations deeply. They understand WooCommerce payment gateway architecture. They reconfigure gateways properly. They test actual transactions. They monitor payment processing. Payments work seamlessly from day one.

Shipping configuration: BigCommerce shipping methods become WooCommerce shipping zones. They set up zones. They configure methods. They set rates. They test shipping calculations. Customers get accurate shipping calculations.

Tax system setup: BigCommerce tax rules become WooCommerce tax configuration. They set up tax rates. They configure tax classes. They handle different locations. They test tax calculations. Taxes calculate correctly.

SEO preservation: They implement proper 301 redirects. Old BigCommerce product URLs redirect to new WooCommerce URLs. They preserve metadata. They maintain URL structure where possible. They handle pagination and filtering. Google understands your site structure.

Understand how they manage BigCommerce to WooCommerce Migration at scale with sophisticated database transformation and zero data loss guarantee.

Testing and staging: They do complete migrations in staging first. They test every product. They test checkout. They test orders. They verify data integrity row by row. They stress test for performance. They load test checkout process.

Performance optimization: They optimize WooCommerce immediately. Database indexing on critical fields. Query optimization. Caching strategy. Image optimization. They monitor performance metrics continuously.

Post-launch support: 90 days of dedicated support. They monitor error logs. They optimize based on real usage. They handle edge cases that emerge.

What makes them technically strong:

Deep BigCommerce proprietary architecture understanding at scale
WooCommerce internals expertise and WordPress architecture knowledge
Enterprise-scale migration experience with thousands of products
Data transformation scripting ability for complex systems
Complex variant system handling and recreation
Performance optimization expertise with indexing strategies
SEO preservation with comprehensive redirect mapping
Post-migration monitoring systems with alerting
Continued technical partnership and support model

2. CMSTOWP

They focus exclusively on ecommerce migrations including BigCommerce. Their entire technical stack is built for migrations. That laser focus means deep expertise.

Cost: Around $25-$99 per hour | Minimum Price: $2,000 or more

CMSTOWP does migrations and nothing else. They've built custom tools. They've solved every BigCommerce edge case. They understand ecommerce migration deeply at the technical level.

Technical approach:

Pre-migration assessment: They thoroughly review your BigCommerce setup. They understand data volume and complexity. They identify third-party applications. They spot performance bottlenecks. They know exactly what they're working with.

BigCommerce database schema analysis: They map every BigCommerce database table. Product tables. Variant tables. Order tables. Customer tables. Custom field tables. They understand relationships completely and document everything.

WooCommerce schema design: They design proper WooCommerce post structure. Product post type optimized for queries. Variants properly structured for filtering. Meta fields indexed for performance. They don't use defaults. They optimize for scale.

Data extraction strategy: They extract from BigCommerce efficiently. They handle massive datasets. They implement intelligent batching for performance. They verify record counts. They do comprehensive spot checks. They validate completely.

Transformation pipeline: They build sophisticated transformation scripts. They handle edge cases. They deal with invalid data. They handle missing values. They maintain referential integrity. They log everything for debugging.

Product migration: They move all products. Thousands. Millions. Whatever volume. They handle simple products. They handle complex variant products. They handle grouped products. They handle bundles. They preserve pricing structures. They maintain stock levels.

Variant transformation: BigCommerce variants become WooCommerce product variations. They map every variant. They handle variant sets. They recreate variant options. They handle variant values. They preserve variant relationships. Custom variants transfer completely.

Custom field transformation: Custom fields become post meta. They map all fields. They handle data type conversions. They preserve all values. Meta is properly indexed. Custom data maintains relationships.

Customer database migration: They create WordPress users from BigCommerce customers. They handle password hashing properly. They understand WordPress password requirements. Passwords work seamlessly. User metadata transfers. User addresses transfer. User preferences transfer.

Order history transfer: Complete order records move with integrity. Order date. Order status. Order items. Item metadata. Customer information. Payment information. All preserved and verified. Customers can view past orders immediately.

Address migration: Billing addresses. Shipping addresses. All transfer with validation. WooCommerce uses them correctly. Customers see saved addresses. They can reuse them. Address format converts properly.

See their technical methodology for complete BigCommerce to WooCommerce Migration with enterprise-scale testing and sophisticated data validation.

Application evaluation: They audit your BigCommerce applications. They identify which are critical to operations. They find WooCommerce plugin equivalents. They set up replacements. They test compatibility thoroughly.

Payment gateway setup: They configure Stripe. PayPal. Square. Authorize.net. Whatever system you use. They set it up properly in WooCommerce. They test real transactions. They monitor payment processing.

Tax configuration: BigCommerce tax rules transfer. WooCommerce tax rates recreate. Taxes calculate properly. Different locations work. Different rates apply. Everything works accurately.

Coupon migration: Discount codes migrate completely. They recreate in WooCommerce. They set up discount rules. They preserve conditions. Existing coupons continue working.

Staging migration: They do complete migrations in staging. You see everything working. You test products. Test checkout. Test integrations. Test everything. Before production.

Zero-downtime deployment: They deploy with zero downtime. They build WooCommerce on the side. They do gradual traffic shifting if needed. They have rollback procedures. Your store never goes offline.

Performance tuning: They optimize WooCommerce from day one. Database indexes on critical fields. Query optimization for common searches. Caching strategy configured. Image optimization implemented. Performance is good immediately.

Security hardening: They harden WordPress security thoroughly. They configure security settings. They set up Web Application Firewall. They implement DDoS protection. Your store is secure.

Post-launch support: Three months of dedicated support. They monitor logs. They optimize based on usage. They fix issues quickly. They handle edge cases.

What makes them technically strong:

Migration-specific tooling for proprietary systems
Deep BigCommerce proprietary architecture understanding at scale
WooCommerce architecture mastery and optimization
Sophisticated data validation approaches with verification
Complex transformation pipeline building capability
Variant system expertise and recreation
Application ecosystem knowledge and replacement strategies
Zero-downtime migration capability and rollback procedures
Performance optimization from day one with monitoring
Security-hardened deployment process implementation
Continuous monitoring after launch with alerting

3. Fixe

A software development and consulting company specializing in ecommerce platform migrations and technical solutions. They understand BigCommerce and WordPress deeply.