Currency and time zone affect billing, reporting boundaries, budgets, and how campaign dates are interpreted. Meta’s current help states that changing these settings creates a new ad account, so this is closer to an account migration than a harmless profile edit. A safe change begins with a reason, a written inventory, and a handoff plan—not with clicking the setting and hoping campaigns continue unchanged.

VISUAL LESSON

What you will learn

  1. 01Determine whether an account-level change is justified.
  2. 02Inventory everything that must be preserved or rebuilt.
  3. 03Cut over with billing, tracking, and reporting checks.
An archived advertising account passes through a protected checkpoint into a newly configured account
A currency or time-zone change deserves a migration checklist because reporting, billing, schedules, and history can cross an account boundary.

ILLUSTRATIVE WORKED EXAMPLE

Scope an illustrative account handoff

Active campaigns inventoriedEvery live delivery path
12
Destinations retestedTwo still block cutover
10/12
Tracking paths verifiedThree need repair
9/12
Ready to relaunchOnly complete rows move
8/12
Illustrative example—not a benchmark. Replace every sample value with your own campaign, market, and measurement data.

PRACTICAL INTERFACE MAP

Move from change request to controlled cutover

Decision01Confirm the reason and consequence

Record the business need, desired currency, reporting time zone, stakeholders, and Meta’s current new-account warning.

Inventory02Preserve the old setup

Capture campaigns, budgets, audiences, creative, destinations, events, permissions, invoices, and reporting baselines.

Cutover03Configure, test, and relaunch

Complete live prerequisites, add billing, rebuild approved campaigns, run labeled tests, and switch only complete rows.

Conceptual walkthrough. Labels, controls, and availability can vary by account, region, plan, and interface version; verify the current screen before acting.

STEP-BY-STEP LESSON

Business reason → preserved evidence → new account → controlled relaunch

DecideNeed and consequences
PreserveSettings and history
Cut overBilling, tracking, delivery

THE LEAD ATLAS METHOD

For the relaunch market, Lead Atlas Data can research a custom list of current business contacts by campaign category and location, while paid-account history and outbound results remain independently measured.See how custom list research works ↗
01

Confirm that an account change is the right fix

Write the actual problem: billing currency, finance reconciliation, campaign-day boundaries, operating region, or an incorrectly created account. Compare an account change with less disruptive fixes such as report scheduling, naming, or finance-side conversion before proceeding.

Open Meta’s current currency and time-zone guidance from the affected account and record the displayed consequences and prerequisites. Because Meta says the change creates a new ad account, obtain finance, campaign-owner, and access-owner approval for the migration window.

02

Inventory the old account

Export or capture account ID, currency, time zone, people and partner access, payment method context, spending limits, invoices, active and scheduled campaigns, budgets, bids, audiences, placements, creative, destinations, tracking parameters, events, attribution settings, and recent performance baselines.

Record which assets can be selected from the new account and which must be recreated or reauthorized. Preserve screenshots and exports with dates; a campaign name alone is not enough to reconstruct nested ad-set and ad settings later.

03

Design the reporting and billing handoff

Choose the intended local reporting day and explain how the time-zone boundary will affect comparisons across the cutover. Define the last reporting window in the old account, the first in the new account, invoice ownership, payment approval, spending limits, and emergency stop responsibility.

Do not splice old- and new-account metrics into one continuous trend without marking the boundary. Currency conversion, tax handling, attribution maturation, and differing day cutoffs can make adjacent periods look comparable when they are not.

04

Create and test the replacement setup

Follow the current in-account workflow and prerequisites, then configure the new account’s access, payment method, limits, pixel or dataset connections, domains, conversions, audiences, campaign structure, URLs, UTMs, and notifications. Rebuild only approved, current campaigns rather than copying obsolete clutter.

Use labeled low-risk tests to verify payment acceptance, review status, delivery eligibility, landing pages, forms, events, CRM routing, notifications, and conversion reconciliation. Confirm that the new account ID is reflected in team documentation and automated reports.

05

Cut over campaign by campaign

Pause or end old-account delivery according to the written handoff, launch only fully verified new-account rows, and monitor spend, pacing, review status, delivery, reporting boundary, conversion receipt, and qualified outcomes. Keep a rollback or stop plan for broken tracking or unexpected billing.

Deliverable: change rationale, live Meta prerequisite capture, stakeholder approval, old-account inventory, access map, billing plan, reporting-boundary note, rebuilt settings sheet, test evidence, campaign-by-campaign cutover log, old-account archive links, and post-launch reconciliation.

THE TAKEAWAY

Treat a currency or time-zone change as a new-account cutover: preserve evidence, follow the live eligibility checks, rebuild deliberately, test billing and tracking, and retain the old account for audit context.

OFFICIAL REFERENCES

Check the platform’s current instructions.

Platform labels, eligibility, and workflows can change. These official help pages were used to validate this lesson.