Recipe: Migrate from legacy v2
The protocol surface has been stable across v2 → current, but the docs IA, package names, and best practices have shifted. This page maps old concepts to new ones.
Concept renames
| Old (v2 docs) | Now |
|---|---|
| dCommerce ecosystem | (removed from dev docs; marketing concept) |
| Boson Protocol v2 | (current protocol, just called "Boson") |
| dApp | The Boson dApp |
| Boson for WooCommerce | WooCommerce plugin |
| Metaverse toolkit | (deprecated) |
| Commit button widget | Commit Widget |
Package map
| Old import | Now |
|---|---|
@bosonprotocol/core-sdk | (same; current version) |
@bosonprotocol/common | (same) |
@bosonprotocol/ethers-sdk | (same) |
@bosonprotocol/metadata | (same) |
@bosonprotocol/ipfs-storage | (same) |
@bosonprotocol/eth-connect-sdk | (unchanged; rarely used) |
| Subgraph clients | (part of @bosonprotocol/subgraph; rarely imported directly) |
The on-chain Diamond is backwards compatible; existing exchanges from v2 continue to work.
Doc URL redirects
The new site doesn't host a /legacy/* namespace. Old links land on a redirect page; key ones map to:
| Old URL | New URL |
|---|---|
legacy-docs/learning-resources/quick-start-tutorials/seller-side/selling-on-the-dapp/* | /build/sellers/dapp |
legacy-docs/learning-resources/quick-start-tutorials/seller-side/boson-for-woocommerce.md | /build/sellers/woocommerce |
legacy-docs/learning-resources/quick-start-tutorials/buyer-side/* | /build/buyers/dapp |
legacy-docs/core-concepts/dispute-resolution.md | /concepts/dispute-state-machine |
legacy-docs/core-concepts/fees.md | /concepts/funds |
legacy-docs/technical-documentation/smart-contracts/architecture.md | /concepts/architecture |
When you'll have to change code
- Import paths: largely unchanged.
configIdadoption: if your v2 integration used per-chain env vars, switch to a singleconfigIdper environment.- Subgraph indexing lag: if you weren't calling
waitForGraphNodeIndexingafter writes, start. See Concepts → Eventing & indexing. - Meta-tx: if you're on Biconomy v1, look at switching to a token-auth meta-tx — fewer steps and cleaner UX.