Migrating from FBTool to Wevion: A Practical, Step-by-Step Plan

Migrating from FBTool to Wevion: A Practical, Step-by-Step Plan

The word "migration" oversells this. There is nothing to move. Your campaigns, ad sets, ads, audiences and pixels live in your Meta ad accounts; any management tool is a layer sitting on top of them. What you are really doing is connecting the same accounts to a different panel, rebuilding a handful of recurring checks, and deciding afterwards which panel you actually open.

This is an operational plan, not a pitch. It says what transfers, what does not, what you have to build from scratch, and how long each part takes. The honest reasons not to switch are at the end, and they are real.

Before you start: what a tool actually controls

Everything in the left column comes with you automatically. Everything in the right column you rebuild — and that is the actual work of the migration, usually two or three afternoons.

Day 1 — connect

1Step 1: create the account

Sign up and start on the permanent free plan at EUR 0: three accounts per platform, one seat, the full campaign launch toolset, Wavo and 14 days of data history. That is enough to run this entire guide as a rehearsal before paying anything.

The price is keyed to how many accounts you manage, not how much you spend — so it does not move when your spend does.

2Step 2: connect Meta through OAuth

Settings → Connected Accounts → Add Meta Account starts Meta's own OAuth flow:

1. You log in on Meta's login page, not ours.
2. Meta asks you to authorise Wevion to manage advertising.
3. You choose which Business Managers, ad accounts and pixels to grant.
4. Meta issues a scoped token. We never see your password, and you can revoke the token from Meta Business Settings at any time without changing it.

3Step 3: connect the other five while you are here

This is the step most people skip on day one and regret on day ten. Meta, Google, TikTok, Taboola, Snapchat and Outbrain all connect the same way, through their own official APIs. Once they are in, insights land every 15 minutes on all six, historical backfill runs, and everything after this point works across the whole plan rather than one channel.

4Step 4: connect the revenue

Also worth doing on day one, because it changes what every later screen shows you.

Nine tracker adapters connect directly — Keitaro, RedTrack, Binom, Voluum, ClickFlare, BeMob, Everflow, ExoClick, TrafficManager — including the ones you self-host. Shopify and WooCommerce come in as full integrations, with refunds attributed down to the individual ad and cost of goods frozen at the order.

From then on the profitability view shows contribution margin per campaign, ad set and single ad, with spend, revenue_gross, revenue_net, refunds, cogs_total, shipping_cost, processing_fees, contribution_profit, contribution_margin, true_roas and break_even_roas. One gap worth knowing before you build a report on it: there is no tax column.

5Step 5: verify the sync

The first sync takes roughly 5–30 minutes depending on volume and history depth. Check five things:

Days 2–3 — rebuild your launch templates

Most teams have three to five templates that account for the large majority of launches. Write those down first: objective, targeting, budget type and amount, placements, creative requirements, naming convention.

Then build them in the bulk launcher, which is a spreadsheet-shaped grid: one row is one campaign, and each row carries its own platform. One sheet can therefore launch on Meta and Google in the same run — the thing a single-channel tool cannot do by construction. Row limits go by plan: 200 on Starter, 1,000 on Pro, unlimited on Plus.

Alongside it: reusable launch templates, campaign drafts you can review before publishing, and a launch rollback that is Meta only — worth knowing now rather than mid-launch.

Test with one account before going wide. Create a campaign from your most common template, confirm it appears correctly in Ads Manager, verify the settings transferred. This catches configuration mistakes before they multiply.

Days 3–4 — turn your recurring checks into rules

Start by writing down what you check regularly and what you do about it. Almost everyone has four:

• pause ad sets when cost per result crosses a threshold;
• raise budget when the return crosses a target;
• kill campaigns that have not left the learning phase within 48 hours;
• get told when spend spikes with no conversions.

Each is a rule. Four that cover most of it:

Four things to know about the engine before you build them:

• Conditions can read 33 metrics, four of which are profit, profit_margin, true_roas and break_even_roas. If you connected your tracker or store on day one, you can write the rule on margin rather than on return. Most engines cannot.
• Rules evaluate every 15 minutes.
• The brake is asymmetric. When you stop autonomy, activations, budget increases and relaunches halt while pause and decrease budget keep running. The safe direction stays open.
• Budget moves are idempotent. A redelivered queue message never doubles the change.

And the counted version, so you build rules that exist rather than rules you wish existed:

On Outbrain you change budgets by hand and through Wavo, just not from the rule engine.

While you are here: two things that are not rules

• Budget Pools. Declare one daily budget, put campaigns from several platforms inside it, and every eight hours by default the pool moves budget toward what is performing — with per-member minimums and maximums, a simulation you can run first, and a log written after. It runs on all six platforms and it is the thing most people expect a rule engine to do and then find it does not.
• Wavo, the copilot. It writes into the accounts on all six platforms; approval-mode tools wait for a human click, executed parameters are re-read from the database rather than the model's message, and default guardrails are EUR 50 per action and EUR 200 per day per team. It will also answer who changed this budget and when out of the audit log, in plain language.

Alerts

Connect Telegram in Settings → Integrations and split the channels: critical alerts, rule notifications, daily summaries. There is a detailed walkthrough for Telegram alerts if you want the full setup.

Days 4–5 — run both, then count

Do not switch off anything yet. Keep both tools open and make all changes in Wevion while the other stays available.

Verify five things during the parallel period:

• changes made in Wevion appear in Ads Manager within seconds;
• bulk operations complete without errors;
• rules fire on the conditions you set;
• alerts arrive where you expect them;
• reported performance matches Ads Manager.

Then decide with a number rather than a feeling. Track how long common operations take in each tool, and — more useful than any table — count how many times you opened each one over three weeks.

Team

Access is structured as organisation → team → workspace → access groups, with data isolation at each level. Two-factor authentication, an audit log you can query in plain language, and support impersonation for when someone on our side needs to see what you see. Published plan limits: 100 workspaces, 50 teams, 200 memberships. Each member connects their own Meta accounts through OAuth, so nobody shares a login.

Budget one extra day for team migration beyond the standard setup.

What you gain, and what you give up

Gain: five more platforms in the same panel and the same subscription; revenue and margin sitting next to the spend; rules that can read that margin; Budget Pools; creative fatigue scoring across all six platforms; competitive intelligence pulled from the Meta Ad Library; roles, workspaces and an audit trail; an MCP server and CLI on one API key from the Pro plan up.

Give up — and check these against your week first:

• The account-recovery workflow. Unban requests and review of rejected ads are in FBTool.pro's published feature set and not in our product.
• Non-advertising Facebook management. Pages and groups are outside our scope.
• A lower entry price. If Facebook is your entire media plan, their entry price is lower and that difference is real money.
• Tax columns in the profitability view.
• Ad-set and ad-level rule actions on every platform — three, as the table says — and launch rollback outside Meta, which is one.

How Wevion connects to Meta

Through Meta's official Marketing API with OAuth: you authenticate on Meta's own page, grant specific ad accounts, Business Managers and pixels, and Meta issues a scoped token. We never see your password.

One thing we will not tell you: that any tool makes an account safe. It does not. Advertisers get restricted for what is in the ad, the targeting and the landing page, and that is between you and Meta whatever software sits in front of it. What we can describe is our own behaviour — official endpoints, server-side rate limiting, and every write starting life as a request that waits for someone to press.

Timeline

Start

The rehearsal costs nothing: the free plan is permanent, so you can connect one account, rebuild one template, write one rule and see the whole shape of it before any money changes hands. If you want the feature-by-feature version first, it is in FBTool vs Wevion.