Moving a Price Monitor to Another Site Without Mixing Up License Timing

When a site move makes the monitoring setup feel more complicated

A WordPress store team can reach a point where the real problem is not the competitor list itself. The problem is where that list now lives. Maybe the site has been reorganized, a store has been moved to a different installation, or the monitoring work now belongs to a different WordPress website under the same account. At that moment, it is easy to assume the cleanest fix is to buy more capacity and sort the rest out later.

That is usually where confusion starts. Oltora Price Monitor – Additional Product Capacity increases monitored-product room for one selected WordPress installation in 1,000-product increments. It does not change the annual license itself. So if you are moving the monitoring workflow to another site, the question is not only how many products that site needs. It is whether you are assigning the add-on to the correct installation before you rely on it.

The objection: “I may be changing sites anyway”

That hesitation makes sense. If a store is being migrated, rebuilt, or split across several WordPress installations, buyers often wonder whether they should wait until everything settles before expanding capacity. Waiting can be the wrong move if the new site already needs the monitoring space now. But buying first without checking the destination site can also be wasteful.

The practical way to think about it is simple: capacity belongs to one selected installation, while the annual license still governs whether the tool remains active. A site move does not turn those into the same decision.

What to check before assigning extra capacity

Before you add capacity, ask three questions about the destination site.

• Is this the WordPress installation that will actually run Oltora Price Monitor?
• How many competitor products does this site need to monitor now?
• Will the current annual license term still cover the period you need the add-on to remain active?

Those checks prevent a common migration mistake: putting more room on the old site because it is still easier to access, while the new site is the one that needs the coverage. The add-on is tied to the selected WordPress website shown in the dashboard, so the destination matters.

Why migration and capacity planning should stay separate

When teams move between installations, they often bundle too many decisions together. Site migration, product-count planning, and license timing can all happen in the same week, but they do not behave the same way.

Capacity planning is about how much competitor coverage one WordPress installation needs. Migration planning is about where that monitoring should live. License timing is about how long the current setup stays active. If you keep those separate, the purchase becomes easier to match to the actual workflow.

That separation matters even more for teams managing more than one site. A single license can cover several activated websites, and each one can have a different monitoring limit. A busy store might need more room, while a quieter site can stay at the default level. The useful question is not “Should every site be treated the same?” It is “Which installation is carrying the heavier monitoring load right now?”

How the 1,000-product increments help in a switching state

The add-on is structured in 1,000-product steps, which makes it easier to match the new site’s actual size. If one site is moving into the role of primary competitor watchlist, you do not have to jump from small coverage to a vague large plan. You can add room in increments that fit the current catalog pressure.

That is especially useful when a migration is temporary in one sense and permanent in another. The website may be changing, but the monitoring need is real today. An incremental capacity increase lets you solve the immediate limit without pretending the broader site transition is already finished.

What this upgrade does not change

The product page is specific about the boundary of the add-on. It increases product capacity only. It does not renew the annual license or extend the term. When the license expires, the additional capacity stops with it.

That is not a drawback so much as a reason to plan cleanly. If the current license term already fits your timeline, extra capacity can help the new installation stay useful during the transition. If the term is close to ending, the smarter move may be to factor that into the broader plan instead of treating the capacity add-on as a separate rescue.

A simple decision path for a moved or switched site

If you are deciding where the extra monitoring room should go, use this sequence:

• Identify the WordPress installation that will actively monitor competitors.
• Estimate the number of products that site needs beyond the default 1,000.
• Choose the quantity that adds the right amount of capacity in 1,000-product steps.
• Check that the annual license term still supports the period you need.

That approach keeps the purchase tied to the actual operating setup instead of the old one you are leaving behind.

If you are managing a migration, a site split, or a handoff between installations, the value of the upgrade is not that it changes the license model. It is that it lets one selected site carry the competitor watchlist it actually needs, without forcing the rest of the account to change with it.

For the product details, see Oltora Price Monitor – Additional Product Capacity.