Meta Ads Agency Handover Checklist: A Safe 30-Day Plan
A practical Meta Ads onboarding and offboarding plan covering access, billing, evidence, tracking, audiences, creative, change control, and the first 30 days.
A Meta Ads handover is not complete when the new agency can open Ads Manager.
The real handover includes business access, Page and Instagram connections, ad accounts, datasets, Conversions API, billing, lead retrieval, audiences, creative rights, current experiments, reporting definitions, and a controlled plan for change.
Handled badly, an offboarding can stop ads, break events, strand leads, lose access to source creative, or destroy the baseline needed to judge the next team. Handled well, it preserves continuity and gives everyone a fair, evidence-based starting point.
This guide works for onboarding a first agency, replacing a provider, or bringing work in-house.
TL;DR
The handover principles
Preserve before improving
The current account contains history, approvals, delivery data, creative evidence, and change records. Preserve it even when the structure needs work.
Access before removal
Confirm business and incoming-team access before removing the outgoing team. An urgent lockout is different; follow the platform’s security and recovery process when compromise is suspected.
Evidence before opinion
Export and annotate the baseline before making major changes. Otherwise the old and new teams can argue about different windows and definitions.
One change owner
During overlap, name who may publish, change budget, edit events, or alter billing. Two teams making live changes creates risk without accountability.
What belongs in the handover
| Area | Confirm | Evidence |
|---|---|---|
| Business portfolio | Business admins and security status | Portfolio ID and access list |
| Facebook Page | Correct ownership and access | Page ID and role list |
| Correct account and Page connection | Handle and connection status | |
| Ad account | Business access, partner access, status | Account ID and permissions |
| Dataset or pixel | Correct website and event source | Dataset ID and diagnostics |
| Conversions API | Integration owner and event path | Method, credentials owner, test events |
| Domain | Business-controlled domain and DNS | Registrar and verification status |
| Billing | Payer, payment method, invoices, limits | Billing owner and open balance |
| Leads | Retrieval, routing, CRM fields, response owner | Test lead and handoff record |
| Audiences | Source, exclusions, purpose | Audience inventory |
| Creative | Final ads, source files, rights | Library and licence notes |
| Reporting | Attribution, funnel definitions, source of truth | Dated baseline export |
Phase 1: Days -30 to -21 — inventory and authority
Start before the end date whenever possible.
1. Name the handover owner
One person at the business coordinates access, deadlines, evidence, and decisions. Finance, legal, web development, sales, and the agencies can contribute without becoming parallel owners.
2. Confirm the contract and timeline
Record:
This is an operational checklist, not legal advice. Use the signed agreement and qualified counsel where needed.
3. Build the asset inventory
List every Meta asset and connected non-Meta system. Include the account ID, owner, administrators, integration, and exit action.
Do not assume the visible ad account is the whole system. A lead campaign may depend on the Page, Instagram, website, dataset, CRM connector, form library, calendar, call tracking, automation tool, and reporting warehouse.
4. Declare a change freeze
Set the freeze window and exceptions in writing.
Freeze:
Allow:
Every exception should have an owner, timestamp, reason, and rollback plan.
Phase 2: Days -20 to -14 — access and security
5. Confirm business-controlled administrators
Maintain at least two current internal administrators on critical business assets. Remove former employees and unknown users after confirming they are not required integrations or system identities.
Meta distinguishes Page full control from task access. Full-control users can manage access and remove others, so assign that level narrowly. Agencies normally receive partner or task permissions appropriate to the contracted work.
Meta also says not to share Facebook logins or use inauthentic shared profiles. Give each person or business its own supported access path.
Official references: Facebook Page access, Meta ad-account roles, and Meta security guidance.
6. Secure the identities
Do not email passwords, backup codes, private keys, or access tokens to the new agency.
7. Grant incoming access
Grant only the assets and permission levels required. Ask the incoming team to confirm access to:
The business owner should verify the same assets independently.
Phase 3: Days -13 to -7 — capture the evidence
8. Export the performance baseline
Use agreed date ranges that reflect seasonality and sales delay. Export:
Do not present platform-attributed revenue as settled cash without reconciliation.
9. Document active experiments
For every live test, record:
The incoming agency can continue, stop, or redesign the test—but the decision should be explicit.
10. Record campaign logic
Explain why campaigns are separate or consolidated:
Names alone rarely explain the strategy.
Phase 4: Days -6 to 0 — billing, tracking, audiences, and creative
11. Validate billing
Confirm:
Do not remove a valid payment method before the replacement is approved and delivery continuity is tested.
12. Validate the dataset and events
Record:
Send controlled test events. Confirm the website, Events Manager, CRM, and reporting layers refer to the same business action.
Meta describes Conversions API as a connection for website, server, app, CRM, offline, phone, and messaging data. It is not a reason to send data without the required rights and notices. Review Meta’s Conversions API overview and Business Tools Terms.
13. Inventory audiences
For each custom or lookalike audience, record:
Do not expect the outgoing agency to deliver an export of individual Meta users from a platform audience. Preserve access to business-owned source data and rebuild permitted audiences inside business-controlled assets when necessary.
14. Transfer creative and approvals
Collect:
Do not duplicate every ad into a new post ID without a reason. Existing ads may carry useful delivery and social-proof context.
15. Test the lead path
Submit a test through each active conversion location:
Verify source capture, CRM creation, assignment, acknowledgement, human response, stage update, and downstream event feedback.
The first 30 days under new management
| Window | Primary job | Output |
|---|---|---|
| Days 1–3 | Confirm continuity | Access, billing, tracking, and lead-delivery sign-off |
| Days 4–7 | Observe and reconcile | Baseline report using agreed definitions |
| Days 8–14 | Fix critical leaks | Controlled corrections with change log |
| Days 15–21 | Launch one priority test | Written hypothesis and decision rule |
| Days 22–30 | Review downstream quality | Qualified, booked, won, and value readout |
Days 1–3: continuity
Do not redesign the whole account. Confirm ads serve as intended, leads arrive, billing works, events remain stable, and urgent policy issues are owned.
Days 4–7: reconciliation
Compare Ads Manager, CRM, call tracking, website analytics, and collected revenue. Differences are expected; unexplained differences need investigation.
Days 8–14: controlled corrections
Prioritize issues that damage decision quality or customer experience:
Days 15–21: one priority experiment
Choose the highest-value uncertainty: creative concept, offer, form, conversion location, qualification, or audience control. Avoid changing all six.
Days 22–30: commercial review
Report the cohort far enough downstream to be useful. Some jobs will still be open; label incomplete cohorts instead of declaring them lost.
Offboarding removal order
Remove outgoing access only after:
1. Business administrators are verified.
2. Incoming access is tested.
3. Billing continuity is confirmed.
4. Lead routing and CRM retrieval work.
5. Dataset and events are stable.
6. Evidence and contracted files are delivered.
7. Open invoices and responsibilities are documented.
8. The final removal date is acknowledged.
Then remove partner, person, application, and system access that is no longer required. Rotate credentials or tokens the outgoing team legitimately knew, without breaking active integrations.
Common handover failures
Rebuilding the account on day one
This destroys the baseline and multiplies variables. Preserve first, then change deliberately.
Removing the old team before checking dependencies
The outgoing partner may own an integration, lead connector, reporting tool, or creative library. Map it before removal.
Keeping both agencies live without a change owner
Overlap can help knowledge transfer, but only one party should control publishing and budget changes.
Assuming Pixel access equals tracking ownership
Website code, server integrations, consent, CRM events, and dataset permissions may have different owners.
Treating handover as proof of poor performance
A provider change can happen for many reasons. Preserve neutral evidence so the incoming team diagnoses rather than inherits a story.
FAQ
Should I create a new Meta ad account when changing agencies?
Usually not. Preserve the business-controlled account and history unless a documented technical, legal, security, or platform reason requires another approach.
How long should agencies overlap?
Long enough to complete agreed access, evidence, and dependency transfer. The right period depends on contract, complexity, risk, and staff availability; there is no universal number.
Should the outgoing agency remove itself?
The removal action can be performed by an authorized party according to the access structure. What matters is that the business confirms continuity first and records the final access state.
Can the new agency change campaigns during the freeze?
Only through the documented exception process for safety, policy, severe waste, or continuity. Routine optimization can wait until the baseline is captured.
What if the outgoing agency will not provide source files?
Check the agreement and documented licences. Published ads, commissioned source files, stock licences, and the agency’s reusable internal systems may have different rights.
What should the incoming agency audit first?
Start with business outcomes, conversion definitions, tracking, lead flow, campaign logic, creative, and access. Use the Meta Ads audit checklist after continuity is secure.
Make the handover evidence-led
I take over Meta accounts without treating the previous structure as disposable. The first job is to preserve evidence, verify tracking and lead flow, then change the constraint that affects commercial performance. See my Facebook Ads specialist service or conversion-tracking service. For a neutral pre-handover diagnosis, send the current setup.
Related guides:
Written by
Vince Servidad
PPC Strategist · Google Ads, Meta Ads & conversion systems
Filipino PPC strategist. A seven-figure Shopify brand and 10+ years across Google Ads, Meta Ads, stores, tracking, and content.
Need help with Facebook Ads?
Get strategic and hands-on support from a PPC strategist based in the Philippines.