How to Move from Nooklz to a Six-Platform Panel

The good news about this migration is how little of it is actually a migration.

Your campaigns, ad sets, ads, audiences and pixels live on Meta's servers. A management tool is a layer on top of them — swap the layer and the objects underneath do not move. What you are really doing is changing where you work from, and rebuilding the automation while you are at it.

This guide covers the move from a Telegram-first Facebook workflow to a panel that covers six ad platforms, using Wevion as the worked example.

---

Before you start: is it the right move?

Worth doing if any of these is true:

• You are running, or about to run, more than one ad platform.
• You need revenue and contribution margin next to spend rather than in a spreadsheet.
• More than one person touches the accounts, and someone will eventually ask who changed what.
• You want rules that can act on profit rather than only on ROAS.

Not worth doing if you are one operator on Facebook only and your day genuinely runs faster from a chat window. A panel would be a bigger machine than your problem.

---

Pre-move checklist (15 minutes)

1. List your ad accounts and note which Business Manager each one sits in.
2. Confirm you have admin rights on the Business Manager — OAuth grants what your own role allows, nothing more.
3. Write down your current automation: every auto-rule, its condition, its action, its cooldown. This is the only thing you actually have to carry across.
4. Note your reporting habits: the two or three numbers you check first every morning. You will want them on the new dashboard on day one.
5. Decide the parallel set: which accounts stay on the old tool while you test, and which move first. Keep the sets disjoint.

---

Step 1 — Connect the account (5 minutes)

Create the workspace, open the connection page for Meta, and authorise through Facebook's standard OAuth flow. Meta issues scoped tokens; they are stored encrypted, and refresh handling is the platform's job rather than yours.

The same page exists for the other five platforms — Google, TikTok, Taboola, Snapchat and Outbrain — whenever you want them. That is the point of the move, and it is worth connecting at least one of them during the test rather than after.

---

Step 2 — Check what appeared (10 minutes)

Within a few minutes of connecting, you should see:

• Every campaign, ad set and ad in the connected accounts, with their current status.
• Historical performance data, backfilled rather than starting from today.
• Audiences, pixels and conversion events.
• Spend and results refreshed on a 15-minute cadence.

What does not appear is anything that never existed on Meta: tool-side profiles, tool-side automation, and any state that only lived inside the previous layer. That is expected, and it is the whole reason step 3 exists.

---

Step 3 — Rebuild the automation (30–60 minutes)

Do not port your rules one for one. Rules written for a single channel and a single metric are rarely the rules you would write with more available.

What the engine can read: 33 condition metrics, four of which are profit, profit_margin, true_roas and break_even_roas. So a pause rule can be written on contribution margin rather than on ROAS — provided your tracker or store is connected, which brings us to the next paragraph.

A sensible first set:

Three behaviours to know before you trust the engine with anything:

• The autonomy brake is asymmetric. Stopping autonomy halts activate, budget increases and relaunch, and leaves pause and budget decreases running — so the brake never traps you in a spending position.
• Budget mutations are idempotent. A redelivered message does not apply the move twice.
• Rules run every 15 minutes, and can be previewed against your own data before you commit.

Where they exist, the actions are: campaign pause and activate on all six platforms, budget moves on five (Outbrain has no branch in the rule engine — there you change budget by hand or through Wavo), cross-platform comparisons on four, ad-set and ad-level actions on three (Meta, TikTok, Snapchat), and relaunch on Meta only.

---

Step 4 — Connect the revenue (20 minutes, and the one that pays for the move)

This is the step people skip and then regret.

• Self-hosted tracker? There are ten adapters — Keitaro, RedTrack, Binom, Voluum, ClickFlare, BeMob, Everflow, ExoClick, TrafficManager among them — each with its own connection screen. Postback revenue lands in the same table as the spend.
• Store? Shopify and WooCommerce, with refunds attributed back down to the ad that produced the order and COGS frozen at the order.

Once that is in, you get contribution margin per campaign, ad set and single ad: spend, gross and net revenue, refunds, COGS, shipping, processing fees, contribution profit, contribution margin, true ROAS, break-even ROAS. There is no tax column — worth knowing now rather than at month-end.

And this is what makes step 3's better rules possible at all.

---

Step 5 — Set up the launcher (30 minutes)

Rebuild one of your recurring launches in the bulk grid: one row per campaign, with the platform as a column, so a single sheet can put Meta and Google live in the same run. Save it as a launch template.

While you are there, set the naming convention. It costs ten minutes now and saves every report you will ever export.

---

Step 6 — Run in parallel (1–2 weeks)

Keep the two account sets separate and watch four things:

1. Do the numbers agree with what Meta's own Ads Manager shows for the same window?
2. Do the rules fire when you expect, and does the log say what they did?
3. Do the alerts still reach you where you read them — Telegram, email, push, in-app?
4. Is the daily check faster than it was, once everything is on one screen?

If the answer to all four is yes after a fortnight, the decision has already been made for you.

---

Step 7 — Consolidate

Move the remaining accounts, cancel whatever the old workflow needed and the new one does not, and write down the new routine for whoever else touches the accounts.

Then do the thing the move was for: connect the second ad platform. That is where the time actually comes back — not from the tool being nicer, but from the second channel no longer meaning a second tool and a manual reconciliation between two exports.

---

Common questions during the move

"I manage a lot of accounts." Account limits scale with the plan, and the free plan starts at three per platform so you can test the workflow before sizing it.

"I need programmatic access." API keys carry per-domain permissions across 22 domains, with an MCP server and a CLI on the same key, from the Pro plan up.

"My team needs different levels of access." Organization → team → workspace → access groups, with data isolation, two-factor authentication and an audit log you can query in plain language.

"I don't want an AI touching my budgets." Then don't switch it on. Wavo's write tools can be left in approval mode, where each action waits for a human click, and the default guardrails are €50 per action and €200 a day per team.

---

Timeline summary

---

The bottom line

Migrating tools sounds heavy and this one is not, because the objects you care about were never inside the tool in the first place. The connection is a click; the fortnight is for trust, not for work.

What you gain is not a nicer interface. It is the second ad platform without a second tool, and the margin sitting next to the spend where a rule can reach it.

The free plan is permanent, so you can do steps 1 and 2 right now without a card: start on the free plan.

---

Related Articles

• Nooklz vs Wevion: A Chat Window, or a Six-Platform Panel
• Nooklz Alternative for Meta Ads: Coverage, Margin and the Second Channel
• Autolaunch vs the Official API for Meta Ads