How to Migrate from MGID to Adgora

How to Migrate from MGID to Adgora

Switching from MGID is not a generic platform swap. It is a set of small decisions, and the first one is simple: do you actually need to move this account now, or only part of it? If you run 3 widget types, one native feed, and a single traffic format, the answer may be different than for an account built around multiple feed units, audience rules, and MGID-only settings. That difference matters.

If your MGID setup is already clean, migration can be quick. If it is layered with special exclusions, custom delivery logic, and old tests you forgot you had, you need a tighter plan. This guide on crypto advertising, monetization & Ad-Tech guides sits in the same practical lane, but here the focus is narrower: how to move from MGID without losing the useful parts of the account.

1. Confirm the migration is worth doing for your specific MGID setup

Start with the account, not the idea. Look at the active widget types, the traffic format mix, and any MGID-only settings you rely on. One publisher may depend on a single content recommendation block that behaves in a very specific way. Another may be using 4 separate placements with different bid logic. Those are not the same migration.

Check whether MGID is carrying campaigns you still want to keep live for 2 more weeks or 2 more months. If the answer is “only one seasonal campaign,” the risk is low. If the account contains several live lines tied to old landing pages, old creatives, and one manual optimization rule that nobody can explain, write it down before anything changes.

There is a practical question underneath all of this: what in MGID is actually working today? If your strongest placements are already inconsistent, moving them blindly will only recreate the inconsistency in a new place. A move from MGID to Adgora should begin with that filter, because a bad setup copied perfectly is still a bad setup.

2. Inventory only the MGID elements that have no direct one-to-one replacement

Not every MGID element needs a perfect clone. Some pieces should be recreated, some should be approximated, and some should be dropped on purpose. That distinction saves time. It also prevents you from wasting a morning hunting for a setting that simply does not map across.

Document the MGID items that are truly specific: custom widgets, special feed ordering, old whitelists, campaign labels that encode a lot of history, and any reporting tag that only makes sense inside MGID. If your team uses 6 labels to describe a single campaign, keep the 6 labels in the notes, but do not bring all 6 into Adgora unless they still help decision-making. A thinner structure is easier to manage.

One useful habit: split the inventory into 3 columns. “Recreate,” “Approximate,” and “Drop.” That sounds basic because it is basic. Yet this one step stops the most common migration mistake, which is assuming every old field needs a home in the new platform. It does not.

For publishers, the same logic applies if you also read about how a crypto ad network for publishers behaves across different placements. The point is not to copy every historical setting. The point is to keep the pieces that still produce revenue.

3. Map MGID delivery rules to Adgora account structure

This is where structure matters more than speed. In MGID, placements, targeting logic, caps, and naming conventions may have been built around how your team grew over time. In Adgora, those same elements should be grouped in a way that lets you read performance in 30 seconds, not 30 minutes.

Take one MGID campaign and write down its delivery rules in plain language. Example: “English traffic only, 2 geos, mobile devices, capped at 1 conversion per user, excluded 5 publisher IDs.” Then map each rule to the nearest Adgora account structure. If a rule can live at the campaign level, keep it there. If it belongs in an ad set or placement group, do not bury it in the creative name. That creates confusion later.

Names should be short and mechanical. Use 3 to 5 tokens if you can. A name like “US-EN-Mobile-Feed-A” is easier to audit than a long sentence with dates, team initials, and old test notes inside it. MGID accounts often grow messy through convenience, not through bad strategy. This is the moment to prune that mess.

If your team has already used a decision guide like CPC vs CPM vs CPA, keep those bidding choices aligned with the new structure rather than rebuilding them ad hoc. The structure should explain the bid, not hide it.

4. Prepare creatives and content assets for Adgora formatting

MGID headlines and thumbnails often carry habits from long-running tests. Some are sharp. Some are only familiar. Before moving them, check which assets still match Adgora’s accepted specs and editorial expectations. This is not a full creative reinvention. It is an edit pass.

Start with the headline list. Cut anything that depends on MGID-specific phrasing or looks too much like a recycled test note. Keep the strongest angle, but rewrite for the new context. If a headline worked because it promised one concrete outcome, preserve that outcome. If it worked because of a format trick, do not assume the same trick will carry over.

Then review thumbnails. A clean 1200 by 628 image may be fine on one side of the migration and too busy on the other. If the image has small text, a cluttered border, or a fake UI frame, test it again before you send budget. Images that depend on microscopic detail usually age badly. So do badges, arrows, and crowded overlays.

Feed-style assets deserve the same check. Some MGID creatives were built to match a content grid closely, while others were designed to stand out with a stronger editorial cue. Adgora may accept both approaches, but your test set should be balanced. Use 2 or 3 variants at first, not 12. Too many creative changes at once will blur the result.

When a creative touches a broader vertical, it can help to think in terms of offer fit, not just design. That is one reason articles on crypto advertising or even mobile app install campaigns are useful references. Different traffic behaves differently. The creative should respect that.

5. Set up a side-by-side comparison window

Do not yank MGID off the board on day 1. Keep it live while Adgora enters the picture, but set the test up carefully. The comparison only tells you something useful if the audiences, placements, and test period are controlled. Otherwise, you are just comparing two moving targets.

Match the audience definition as closely as possible. If MGID is running on English-speaking desktop readers in 2 countries, do not test Adgora on mobile-only traffic in 5 countries and call it a comparison. That is a different audience. Use the same geo set, the same device split, and the same time window if the inventory allows it. Even a 7-day overlap is better than an unstructured rollout.

Placement matching matters too. If MGID has 4 publishers or 4 widget positions that produce most of the volume, choose equivalent placements first. You want a controlled test, not a broad launch disguised as a test. One placement can behave differently from another for reasons that have nothing to do with the platform.

Keep budgets small at the start. The point of the comparison window is to measure direction, not to force scale on day 1. If one side is clearly weaker after 48 hours, you have learned something. If both are noisy, extend the test rather than guessing. Guessing is expensive.

6. Verify tracking continuity before moving budget

Tracking is the part that breaks most often, and it only takes one missing parameter to make the data look wrong. Before you move serious budget, confirm that the same postback, UTM, or analytics logic still captures conversions correctly in Adgora after the switch. That sentence sounds basic because the failure is basic too.

Check the full path once, not just the front end. A click should arrive with the right source tags. The landing page should preserve those tags. The conversion should fire once, not twice. If your system uses a server postback, send a test conversion and compare the event in the tracker with the event in Adgora. If the numbers disagree, stop there.

Keep the tracking notes plain. List the parameter names, the destination URL, the conversion event name, and the fallback analytics method if the postback fails. Do not depend on memory. In migration work, memory is often the thing that lies first. A clean log helps if you need to compare 2 days of data after launch.

For teams that manage broader monetization stacks, the same discipline applies elsewhere too. The ad tech glossary can help keep terms straight, but the real work is still in the parameter check. If the tracking is wrong, every optimization note after that is suspect.

7. Decide what to retire, pause, or keep running in MGID

Shutdown is not a dramatic final step. It is a checklist. Pause the campaigns that have already been replaced, keep untouched anything still needed for reporting or historical comparison, and avoid deleting old data too soon. Once data is gone, you cannot rebuild last quarter’s context from a screenshot.

Pause in layers. Start with the weakest MGID campaigns, then move to duplicated tests, then to the campaigns that Adgora now covers well. Leave any active comparison line running until you have at least 1 clean reporting cycle. If your team needs historical access for finance or client review, keep the account alive even if spend is near zero. A dormant account is still useful.

There is one small but annoying risk: internal confusion. If 2 people can still launch in MGID while 2 others are already working in Adgora, someone will make a change in the wrong place. So assign one owner for the old account and one for the new account. That is enough. Put the handoff date in writing.

If the migration touches a broader revenue plan, it can help to review adjacent material like monetize your website with crypto later, but the immediate task is simpler: keep the MGID account readable while Adgora becomes the working system. One active platform, one archived platform, one owner each. That is the cleanest end state.