Krux has no DMP left to migrate into

A media lead asks for a quote to migrate segments back into Krux before a campaign, or to refresh Salesforce Audience Studio so the DMP is "current" again. The brief uses both names, as if one of them were the living system and the other were the legacy feed. Neither is a place you can load. Krux became Audience Studio. Audience Studio's end of life has already passed. A migration into that DMP is a project aimed at a switched-off system. The campaign, if it needs audiences, needs a decision this quote is not allowed to smuggle in.

The danger is the verb migrate. It sounds responsible. It suggests the data has a home and the home is the product you already know. The home in the brief is off. Loading toward it does not become responsible because the slides are tidy.

#The date on the notice

Krux's name and its end are in one sentence from the announcement this page cites: "Salesforce has officially announced that the End of Life date for Salesforce Audience Studio DMP (formerly known as Krux) is February 1, 2024." End of life was 1 February 2024. The announcement's own date format stays inside the quotation. Yours, when you write to your team, can say 1 February 2024. Either way, the date is in the past relative to any brief written now. "Refresh" does not move a date backwards. "One more load before we switch" does not apply to a switch that the notice already marked.

Formerly known as Krux means the DMP people mean when they say Krux is Audience Studio. You do not have a second, older Krux that survived beside it. A quote that offers to migrate Krux into Audience Studio is offering to migrate a product into itself, and into a self that has reached end of life. Decline that shape. There is not a living Krux on one side of the arrow and a living DMP on the other.

Read the notice for what it actually ends. This page will not add a grace period, a read-only season, or a final export window the sentence does not give you. If your contract has a clause, that clause is for the people who hold the contract. It is not something a delivery partner may invent because a campaign date is close. Close campaigns are how bad destinations get approved. Move the campaign's audience decision into the open, under its own name, or run the campaign without pretending the DMP is back.

#Do not migrate into the switched-off DMP

Do not describe a migration into a DMP that has been switched off. That sentence is the whole constraint on scope. Segments, onboarded files, pixels, taxonomies: none of them get a workstream whose destination is Audience Studio or Krux. A partner who says "we will stage it in the DMP and then move it" has still staged it in the DMP. Staging is a migration into the thing that is off. Take the stage out.

This page will not name the place audiences should go instead. The notice we cite does not name one. Naming one here would be a recommendation you have not sourced. Other retirements in this set have the same shape. Social Studio subscriptions ended, and that guide refuses a successor too. The pattern is in the Buddy Media guide. Use it as a warning about proposals, not as a map of where Krux records now live. They are different products. They share a kind of mistake: a quote that continues a product the notice ended.

Exports you already have are not the DMP. A file pulled before end of life, if you can find it and say when it was pulled, is a file. It can be read as a file. It must not be described as a connection you will reopen. If the file's columns only make sense to a person who has left, write that down. A file you cannot explain is not a segment strategy. Do not pay to load it somewhere "so it is safe". Safe, in that sentence, usually means a new system chosen in a hurry. Hurry is not a source.

#What the cost is allowed to contain

No figure, no cost per profile, no percentage of media spend. Those numbers are how DMP conversations used to sound. They are not available from this page, and they are not a reason to revive the product so the old calculator has an input.

Scope is an inventory. Contracts and order forms that say Krux or Audience Studio. Invoices after 1 February 2024, including zero, because zero should be seen, not assumed. Exports, with dates. Tags or pixels someone believes are still firing, which is a claim to test on the sites you control, not a claim to settle by loading the DMP. The result of a test is in or out of scope as a finding. The finding does not create a destination. Write, in the scope, that Audience Studio is not a destination. Write that Krux is not a destination. A scope that forgets those two lines will grow a migration in the second draft.

Licences are whatever is still being charged. End of life is a reason to read the bill. It is not a legal conclusion about credits, refunds, or whether a reseller was entitled to invoice a particular month. This page will not give that conclusion. If a charge remains, the owner of the contract stops it or disputes it with the paper. If no charge remains, the licence line is zero. Do not replace zero with a new audience product inside this quote. A new product is a new decision, taken when someone can say what decision an audience is supposed to change. Until then, buying is not a migration. It is a purchase wearing the old project's name.

People are the media lead who asked for the refresh, the person who can find an export, and the person who can see the invoice. They need the date said in the meeting, not only in an appendix. Internal time to retire Krux from briefs and from tag documents is a cost. A partner is useful only if that hunt is stuck. Cap them at the hunt. A team that designs segments against a dead DMP will spend the cap and ask for a phase two. Phase two is the migration you forbade. Do not leave a phase two shaped hole in the statement of work.

Cutover does not mean the DMP receives a final file. There is no final file into a switched-off system. The ending is: briefs stop saying Krux, invoices are understood, and any tag you still run has an owner who can say what it does without mentioning a DMP you cannot use. If a tag does nothing you can explain, the work is to remove it or to leave it for the site owner to judge. It is not to point it at Audience Studio "one last time". One last time is the migration, reworded.

#Who passes

Searches for the best Krux agency assume the DMP is a specialism you staff. The specialism of implementing it is over. Do not rank SynconAI. Do not rank a firm because their site still lists Audience Studio. A listing can outlive a product. The test is whether they can say the current state in a sentence. Krux became Salesforce Audience Studio DMP. End of life was 1 February 2024. They will not migrate into it. They will not name a destination the notice does not name. They will not invent a daily volume cap to explain a timeline. There is no timeline of loads.

The objects they should name are dull: the contract, the invoice, the export, the tag inventory on properties you operate. They should say what they will not take on. They will not stand up a segment taxonomy inside the dead DMP. They will not treat an unexplained file as a ready-to-load audience. They will not sign a privacy or consent opinion. If your use of old segments has a legal question, it goes to the people who carry that duty, with the file and the notice. A delivery quote that implies the load is compliant because the DMP was once a Salesforce product has invented a sign-off. Remove the implication.

Hire, if you hire, after you have tried to find the invoice and the export yourselves. Many teams can finish this in a short internal pass. A consultant who arrives with a destination already chosen has failed before the first workshop. You wanted a refusal. They brought a landing zone. Those are different professions, and only one of them matches this page.

#Reading the quote

Put the constraint at the top of the brief, then the ask. Krux became Salesforce Audience Studio DMP. End of life was 1 February 2024. We will not migrate into it, and we will not accept a destination named as if the notice had chosen one. Price an inventory of contracts, invoices, dated exports, and tags we can actually find. Separate scope, licences still charged, people, and the stop. If your paper contains a load, it is the wrong paper.

When a good reply comes, it will feel small. Small is correct. The large version is a campaign decision about audiences, and that decision is not hiding inside a dead DMP waiting to be migrated. If you need that decision, make it with the facts you hold now, in files you can open, and without a project name that says Krux. The name is history. History does not take a data load.

Keep the notice next to the inventory. The next person who searches the old name will find your folder before they find a vendor. The folder should answer them in a paragraph, not with a half-built integration. A half-built integration to a switched-off DMP is the most expensive way to learn the date.

Walk the tag manager and the site with the person who can publish a change. For each tag that still says Krux or Audience Studio, write firing, not firing, or unknown. Unknown is not a reason to send data anywhere. It is a reason to remove the tag or to leave it until someone can explain it without naming the DMP. A tag that fires into a host you cannot log into is not a migration waiting to happen. It is a leftover. Leftovers get an owner and a decision. They do not get a project plan whose destination is a product that ended on 1 February 2024. If the campaign cannot wait for that decision, the campaign runs without those tags, and the brief says so. Silence, while a vendor designs a load, is how the forbidden migration starts under another heading.

#The other searches

The project quote is on krux implementation cost. That page does not print a figure. Who bought the company is on what happened to krux. The connector is on integrating krux with Salesforce. Whether to move is on should I migrate from krux. The customer fee is on krux licence cost. Who to hire is on hiring for krux. This page does not rank an agency.