Switching from BQool to Ascent should not be treated as a copy-and-paste exercise. The risky part is rarely creating a new account. The risky part is moving years of pricing assumptions, exception rules, and spreadsheet habits into a new repricer without checking whether they still protect margin.
A good migration does three things at the same time:
If you are already comparing the two tools, start with the commercial page first: BQool vs Ascent. Then use this playbook to decide whether your setup is ready to move.
The short version
| Migration question | Better answer |
|---|---|
| Should we clone every existing BQool rule? | No. Preserve the logic that still matches the business and discard inherited noise. |
| What should be checked first? | Floors, landed cost assumptions, competitor treatment, fulfilment differences, and sensitive SKUs. |
| When is Ascent a stronger fit? | When UK fit, clearer floor control, and a cleaner migration path matter more than keeping a familiar workflow. |
| What should stop the switch? | Poor cost data, unclear ownership, or a team that cannot explain the current rules well enough to rebuild them safely. |
The goal is not to move quickly for the sake of movement. The goal is to move without creating a pricing system nobody trusts.
Before switching, audit the BQool setup you already have
A migration is the perfect moment to separate useful pricing logic from old operating debt.
Review the current account in five areas:
| Area to audit | What to look for | Why it matters during migration |
|---|---|---|
| Minimum prices | Floors based on stale supplier costs, missing fees, or old margin assumptions | A repricer can only protect the floor you give it |
| Rule groups | Overlapping rules, duplicate strategies, or legacy exceptions nobody owns | Messy groups become harder to debug after moving |
| Competitor treatment | Rules that follow every competitor too closely near the floor | Weak competitor filters can turn automation into margin leakage |
| Fulfilment logic | FBA and FBM offers treated as if they have the same economics | Fulfilment method changes cost, Buy Box pressure, and service expectations |
| Sensitive SKUs | High-risk, low-margin, seasonal, or supplier-constrained lines | These need staged handling rather than broad account-wide changes |
If the audit feels uncomfortable, that is useful. It means the switch should include cleanup, not just transfer.
Do not migrate the mess
The easiest migration mistake is to recreate the old account too faithfully.
Sellers often carry across:
That is not a migration. It is moving the attic into a new house.
A better approach is to rebuild rule families around current commercial behaviour:
| Rule family | Keep if | Rebuild if |
|---|---|---|
| Core competitive SKUs | The floor is current and the competitor logic is understood | Operators cannot explain why prices move |
| Low-margin wholesale lines | Costs, fees, VAT treatment, and target profit are current | Floors are maintained outside the repricer |
| FBA lines | Fulfilment costs and Prime positioning are built into the strategy | FBA is being priced like FBM |
| FBM lines | Shipping, handling, and service promises are reflected | FBM is copied from a generic account-wide rule |
| Protected or awkward SKUs | There is a clear reason for the exception | The exception exists because nobody wants to touch it |
This is where intelligent repricing matters. Better automation is not only faster reaction. It is clearer judgement inside the guardrails you set.
Protect floors before you connect broad automation
Minimum price discipline is the migration control that matters most.
Before switching tools, rebuild floors from the inputs the business actually uses today:
Do not assume that an old floor is safe because it has not caused visible damage yet. The floor may only look safe because the team has been compensating manually.
A simple rule: if nobody can explain how a floor was calculated, do not migrate it blindly.
Use a controlled pilot instead of a dramatic cutover
A safer switch starts with a small enough section of the catalogue that the team can inspect behaviour properly.
Choose SKUs that reveal how the repricer behaves under different conditions:
| Pilot SKU type | What it tests |
|---|---|
| Stable repeat sellers | Whether ordinary pricing behaviour feels predictable |
| Thin-margin lines | Whether floors are respected under competitive pressure |
| FBA offers | Whether fulfilment advantage is handled sensibly |
| FBM offers | Whether shipping and service differences are reflected |
| Awkward exceptions | Whether the new rule structure is clearer than the old one |
During the pilot, review price movements against commercial logic, not only whether prices changed. The useful question is: can the team explain the movement and still defend the margin?
What to document before the move
Create a short migration note before changing live behaviour. It should be plain enough that an operator can use it later without needing the person who configured the account.
Include:
This does not need to become theatre. It just needs to stop the account becoming folklore.
Where Ascent usually fits after BQool
Ascent is usually strongest for sellers who want the migration to produce a cleaner operating model, not just a different interface.
The fit is strongest when the seller wants:
That is why the best path is usually:
1. compare the commercial fit on BQool vs Ascent
2. map your current BQool rules into current business logic
3. rebuild floors before connecting sensitive SKUs
4. use intelligent repricing only after the guardrails are clear
The point is not that every BQool user should switch. The point is that if you do switch, Ascent should help simplify the operating model rather than inherit the old clutter.
Who benefits most from switching
Switching is most likely to make sense when:
If your existing setup is stable, easy to explain, and actively protecting margin, there may be no urgency. Good migration discipline includes knowing when not to move.
When not to switch yet
Pause the migration if:
Annoyance is a reason to investigate. It is not enough reason to risk live pricing behaviour.
Final takeaway
The safest way to switch from BQool to Ascent is to treat migration as a repricing cleanup project. Audit the old setup, rebuild floors from current economics, retire rules that no longer serve the business, and roll out through a controlled pilot before touching the full catalogue.
If that sounds like the move you need, start with BQool vs Ascent, then use intelligent repricing as the next lens for deciding how much automation your catalogue is ready to trust.
Related Resources
Explore Ascent Features:
