Device42 Transformation / Migration Pricing - up to 30% off list
Whatever figure Device42 puts on a Transformation / Migration quote, up to 30% of it stays in your budget — that is the position Stackingo holds as an authorised Device42 reseller, with a contractual floor of 10%. There is no cash figure to lead with beyond that, and saying so is the honest starting point: Device42 Transformation / Migration Pricing is quote-only, because the capability is delivered by the Application Discovery & Dependency Mapping add-on and no list rate for it is published anywhere we could reach. The saving is the one number you can rely on before a quote exists, and it applies across the GCC, UK & Ireland, Europe, Oceania and the US.
What you will pay: Device42 Transformation / Migration Pricing at a glance
There is no rate card to read from, and no honest way to manufacture one. Device42's pricing page is a request form, its licensing documentation defines unit mechanics and then defers to a purchasing FAQ that returns a 404, and neither the AWS nor the Microsoft marketplace listing carries a priced entry for the module. So the table below states what is actually true: a quote-only line, and a discount position that attaches to whatever figure Device42 sets. Treat that as useful information rather than evasion. It means the number is negotiable, and that the real work sits in scoping the application host count properly before anyone quotes it.
Line item | List (per month) | Stackingo (per month) | What the quote covers |
Device42 Transformation / Migration (Application Discovery & Dependency Mapping add-on) | On request | Up to 30% below list | ADM enabled on an existing Device42 Core licence and counted on application hosts rather than on total device units. The quote is built from the number of hosts inside the migration scope and the term you need them discovered for, so two organisations with identical estates can be quoted very differently. |
One figure does circulate, and it is worth naming so that you can set it aside. Vendr publishes a median observed Device42 contract value with a wide range around it, and buyers occasionally treat that as a price. It is not one. It is negotiated enterprise spend across an entire platform deployment — Core, add-on modules, term length and volume folded into a single annual commitment — and it says nothing about what the ADM add-on lists at for an estate the size of yours. This page deliberately does not repeat it. What does carry across every deal size is the discount position: up to 30% below the Device42 list figure on your own quote, with a contractual floor of 10%, on identical licensing provisioned into your own instance.
What Device42 Transformation / Migration plans can you buy?
Most of the migration-discovery category sells you a plan and hopes you do not read the metering underneath it: an edition ladder with a rate per tier, then a separate consumption charge for the agents that do the actual work. Device42 charges differently. There is no transformation edition, no migration tier and no published plans page to hold against a rival's. What exists is a Core platform licence banded on discovered device units, and a set of add-on modules bought against it. For this use case the pieces that matter are these — all quote-only, all carrying the same Stackingo position:
Device42 Core — On request, up to 30% below list. The mandatory base licence, banded on discovered device units: physical and virtual machines, containers, cloud instances, archived records and stored terabytes each convert to units at published ratios. No module can be bought without it underneath.
Application Discovery & Dependency Mapping — On request, up to 30% below list. The add-on that actually delivers transformation and migration work: application-to-host mapping, service dependencies and move-group planning. Counted on application hosts rather than on total device units, which is the single most consequential detail on this page.
Software License Management and Power & Environmental Monitoring — On request, up to 30% below list. Two further separately licensed modules, both counted on total device count rather than on application hosts. Neither is required for a migration, and both are worth excluding in writing so that they do not arrive inside a bundled total.
Term length — the variable that behaves most like a plan. A migration is a programme with an end date; a Device42 subscription is an annual commitment. Whether ADM runs for one year or three moves the total more than anything else on the quote, and it is the choice buyers most often leave the vendor to propose for them.
Comparing plans across vendors therefore becomes an exercise in normalising metrics rather than reading tiers. A competitor quoting per agent, per socket or per discovered flow is not describing the same thing as a Device42 quote counted on application hosts, and a spreadsheet that lines the two up column by column will mislead whoever signs it. Before comparing anything, get each vendor to state the countable unit, the ceiling that unit is measured against, and what happens when the count moves mid-term. Stackingo builds that comparison as part of quoting, because a discount applied to the wrong metric is not a saving at all.
What is a Device42 Transformation / Migration subscription and how does it work?
The sequence is short and it rarely varies. You describe the estate — total device units for Core, application hosts for the migration scope — and a quote comes back covering both lines. One annual agreement is signed. The Core licence is provisioned first, discovery runs against the estate, and the ADM module is enabled on top of what Core has already found. From that point a Device42 Transformation / Migration subscription behaves like any other annual software commitment: a fixed term, a fixed entitlement ceiling and a renewal date. Nothing in it is metered by how many applications you eventually map or how many move groups you end up running.
What that sequence quietly hides is a timing decision. Migration discovery is at its most valuable in the months either side of a cutover and considerably less so afterwards, so the real question is whether the subscription should end when the programme does or continue as a permanent operational dependency map. Both are defensible; they are not the same purchase. Decide before signing, because extending a term mid-programme is a negotiation entered from a weak position, while committing to three years for a nine-month wave is money spent on reassurance. Stackingo scopes the term against the programme plan rather than against whichever renewal date is administratively convenient.
Who needs Device42 Transformation / Migration licenses, and how many?
Work it through in the order the counting actually happens. First, discovery runs and Device42 resolves the estate into device units — one physical or virtual machine as a unit, ten containers as a unit, a hundred archived records as a unit, fifty terabytes as a storage unit — and that total sets the Core band. Only then does the second count begin: of those units, which ones host applications inside the migration scope. That second and usually much smaller number is what Device42 Transformation / Migration licenses are counted against, because the ADM add-on is licensed on application hosts and not on the estate as a whole.
Two practical consequences follow. Nobody consumes a licence by using the product: architects, migration leads, application owners and the programme office can all read dependency maps without changing the bill, because no part of Device42 is counted per user. And the number that drives cost is scope-defined rather than estate-defined, so a disciplined wave — the hosts moving this year, rather than every host you own — is materially cheaper than an all-you-can-map entitlement. Agree the wave definition with application owners before requesting a quote, and the licenses you buy will match the work in front of you instead of the wish list behind it.
Where should you buy Device42 Transformation / Migration?
The common mistake is treating the vendor's quote form as the only door, filling it in with a rough device count and accepting whatever returns as the price. It is not a price. It is an opening position assembled from the numbers you volunteered. Buyers who buy Device42 Transformation / Migration that way routinely discover two things too late: that the ADM line was scoped against total devices rather than application hosts, and that a module they will never switch on arrived inside the bundle. Correct both before the quote is drawn rather than after it is signed, because an executed agreement is a poor place to relitigate a metric.
The better route is to buy Device42 Transformation / Migration through an authorised reseller who quotes the lines separately and shows the Device42 list figure, the Stackingo figure and the saving against each one. What lands in your instance is identical either way — the same genuine licensing, the same modules, the same support entitlements — so the only variables are the commercial line and who maintains it afterwards. Insist that Core and ADM appear as itemised lines rather than as a single total. A bundled number cannot be audited by anyone in finance, and it cannot be renegotiated piece by piece at renewal either.
What should a Device42 Transformation / Migration reseller do for you?
Take a realistic shape. An estate resolves to roughly 900 device units, of which 260 are application hosts inside the first migration wave. Two counts, two lines: Core banded on the 900, ADM counted on the 260 — a countable base a little under a third the size of the estate. Now apply the arithmetic that is knowable before any quote exists. The Stackingo position is up to 30% below the Device42 list figure with a contractual floor of 10%, so the negotiable band on both lines is twenty percentage points wide, and where you land inside it turns on term, volume and how tightly that wave has been scoped. A Device42 Transformation / Migration reseller earns its place by moving you up that band rather than by forwarding the vendor's first number.
The rest of the job is unglamorous and worth more across three years than the signature-day discount. It means checking the discovered unit count against your entitlement before renewal rather than after a true-up notice arrives, flagging when a completed wave means the application host count should fall, and holding the discount position instead of letting it erode a point per cycle. Ask any prospective reseller who owns the renewal conversation, what happens when the count moves mid-term, and whether entitlement reconciliation goes in writing. Those three answers separate a reseller from an order-taker faster than any accreditation badge on a website.
What does being a Device42 partner actually mean?
Follow what actually happens when a purchase runs through an authorised channel, and the word stops being decorative. The partner registers the opportunity with the vendor, which is what puts a structured discount position on the table instead of an ad hoc markdown. The quote is then built against Device42's own licensing rules, the order is placed on paper the vendor recognises, and licensing is provisioned directly into your instance — not resold second-hand, not sub-licensed, not repackaged. Renewal afterwards sits with the same Device42 partner rather than reverting to a generic vendor renewals desk that has never seen your migration plan. Stackingo operates on exactly that footing.
The distinction only becomes visible in year two. An unstructured discount is a favour, and favours are not inherited by whoever handles the account next; a programme position is contractual, which is why an up-to-30% ceiling and a 10% floor survive a change of contact on either side of the relationship. Consolidating the wider estate under one Device42 partner has the same quiet payoff. Core, ADM and any module added later sit on one agreement with one anniversary, instead of drifting onto separate renewal dates that nobody reassembles until a budget round forces the issue.
How a Device42 Transformation / Migration distributor simplifies procurement
A distributor takes the administrative weight of a multi-line, multi-region software purchase off your team, and on a Device42 migration that weight is real rather than notional. One agreement covers Core and the ADM add-on instead of two conversations running on two timelines. One invoice arrives in your local currency at a rate fixed on the day of quotation. One renewal calendar governs the lot. A Device42 Transformation / Migration distributor also carries the entitlement reconciliation — matching discovered device units and application hosts against what was actually bought — which is the task most likely to be deferred in-house until a true-up makes it urgent.
Stackingo runs that across the GCC, UK & Ireland, Europe, Oceania and the US under a single agreement, which matters most to organisations migrating estates that sit in more than one region. Separate contracts per country mean separate anniversaries, separate currencies and separate reconciliations, and by year three the cost of that fragmentation is usually larger than the headline discount. None of it changes what is delivered into your instance. It changes how many hours of a migration programme go on procurement administration instead of on move groups, which is the line nobody budgets for and everybody ends up paying.
How much does Device42 Transformation / Migration cost outside the US?
Device42 quotes and invoices in US dollars, which becomes awkward the moment a migration budget has to clear an approval committee that works in dirhams, pounds or euros. Because no list figure is published, the table below cannot convert one. What it can do is set out the currencies Stackingo quotes in and confirm that the same up-to-30% position applies in each of them. The rate that binds is the one fixed on the day your quote is issued, not one lifted from a rate feed weeks earlier. Ask for the local-currency figure and the US dollar figure on the same document, so finance can check the conversion rather than take it on trust.
Market | Currency | List (per month) | Stackingo (per month) |
Australia | AUD | On request | Up to 30% below list |
Austria | EUR | On request | Up to 30% below list |
Bahrain | BHD | On request | Up to 30% below list |
Belgium | EUR | On request | Up to 30% below list |
Bulgaria | EUR | On request | Up to 30% below list |
Croatia | EUR | On request | Up to 30% below list |
Cyprus | EUR | On request | Up to 30% below list |
Czechia | CZK | On request | Up to 30% below list |
Denmark | DKK | On request | Up to 30% below list |
England | GBP | On request | Up to 30% below list |
Estonia | EUR | On request | Up to 30% below list |
Finland | EUR | On request | Up to 30% below list |
France | EUR | On request | Up to 30% below list |
Germany | EUR | On request | Up to 30% below list |
Greece | EUR | On request | Up to 30% below list |
Hungary | HUF | On request | Up to 30% below list |
Ireland | EUR | On request | Up to 30% below list |
Italy | EUR | On request | Up to 30% below list |
Kuwait | KWD | On request | Up to 30% below list |
Latvia | EUR | On request | Up to 30% below list |
Lithuania | EUR | On request | Up to 30% below list |
Luxembourg | EUR | On request | Up to 30% below list |
Malta | EUR | On request | Up to 30% below list |
Netherlands | EUR | On request | Up to 30% below list |
New Zealand | NZD | On request | Up to 30% below list |
Northern Ireland | GBP | On request | Up to 30% below list |
Oman | OMR | On request | Up to 30% below list |
Poland | PLN | On request | Up to 30% below list |
Portugal | EUR | On request | Up to 30% below list |
Qatar | QAR | On request | Up to 30% below list |
Romania | RON | On request | Up to 30% below list |
Saudi Arabia | SAR | On request | Up to 30% below list |
Scotland | GBP | On request | Up to 30% below list |
Slovakia | EUR | On request | Up to 30% below list |
Slovenia | EUR | On request | Up to 30% below list |
Spain | EUR | On request | Up to 30% below list |
Sweden | SEK | On request | Up to 30% below list |
United Arab Emirates | AED | On request | Up to 30% below list |
United States | USD | On request | Up to 30% below list |
Wales | GBP | On request | Up to 30% below list |
Frequently asked questions
What does Device42 Transformation / Migration cost in the US?
There is no published US price. Device42's pricing page is a quote-request form, its licensing documentation defines units without amounts, and the marketplace listings carry no priced entry for the module. What Stackingo, an authorised Device42 reseller, commits to in advance is the discount: up to 30% below whatever list figure Device42 sets, with a contractual floor of 10%.
Why is there no rate card for this module?
Because Device42 sells a banded platform licence plus add-ons, and prices each engagement from the estate it discovers. Every route we checked ends at a form — the pricing page, the licensing documentation, and a purchasing FAQ link that returns HTTP 404. Publishing a figure would mean inventing one. The discount, by contrast, is contractual: up to 30% off list, floored at 10%.
Is Transformation / Migration a separate product from Device42 Core?
It is a separate add-on rather than a separate product. Application Discovery & Dependency Mapping delivers the use case and requires a Device42 Core licence underneath it, so a migration quote should always show two lines. Stackingo applies the same up-to-30% discount to both of them, not only to the base licence.
What is the Transformation / Migration add-on counted on?
Application hosts — not total device units, and never users. Core is banded on discovered device units, while the ADM add-on is counted on the number of application hosts in scope, which is usually a far smaller number. Getting that distinction written into the quote can be worth more than the up-to-30% discount applied to a wrongly scoped line.
Should I use the median contract value I found online as a budget?
No. Published median contract figures for Device42 describe negotiated enterprise spend across a whole platform deployment, with a wide range around them, and none of them is a list price for this module. Build the budget from your own application host count instead, then apply the position Stackingo guarantees: up to 30% below list, with a 10% minimum.
Does the discount survive if the migration scope changes mid-term?
Yes. The up-to-30% position and its 10% floor are contractual and apply to licensing added during the term, so hosts brought into a later wave join at the discounted rate rather than reverting to the Device42 list figure. Stackingo reconciles entitlement against discovered counts ahead of each renewal rather than after a true-up notice.
Is Stackingo authorised to sell Device42 licensing, and where?
Yes. Stackingo is an authorised Device42 reseller supplying genuine Device42 licensing with managed provisioning, entitlement reconciliation and renewal tracking across the GCC, UK & Ireland, Europe, Oceania and the US — at up to 30% below list, with a contractual floor of 10%.
Related Stackingo pricing guides
Worth pricing alongside it: Device42 DCIM Pricing, Device42 ITAM Pricing, Device42 IT Operations Pricing and Device42 Compliance & Audit Pricing all run off the same Core licence and share the same discount position, so a quote covering several use cases is usually one quote rather than four. The Device42 product page carries the transactional overview, or you can skip straight to a quote request scoped to your own application host count.
Ready to put a number against your own migration wave? Send Stackingo your device unit estimate and the application host count in scope, and a tailored Device42 Transformation / Migration Pricing quote comes back with Core and the ADM add-on itemised separately — genuine Device42 licensing, up to 30% below list with a contractual floor of 10%, and renewals managed for you across the GCC, UK & Ireland, Europe, Oceania and the US.
