Changing agencies should not interrupt the moving company's phones, forms or access to its own operating history. Prepare a controlled handover before permissions change. The goal is to preserve usable records and continuity, not to download every available file or share credentials in a large email thread.
View full-size graphic ↗Separate account control from exported files
Scroll the table horizontally to compare all columns.
| Area | Control to confirm | Records or documentation to preserve |
|---|---|---|
| Website and domain | Business-authorized administration | Hosting, DNS and release procedures |
| Advertising | Appropriate owner access and billing clarity | Campaign history, settings and change context |
| Analytics and tags | Administrative access and configuration ownership | Event definitions, tags and reporting notes |
| Calls and forms | Number/routing and delivery continuity | Source mappings and integration requirements |
| CRM and reporting | Authorized access and export rights | Field dictionary, relevant records and dashboards |
| Creative assets | Usage rights and source-file availability | Approved assets and permission records |
An export does not replace administrative control, and administrative control does not guarantee that all historical records remain available. Review both. Confirm contractual rights and responsibilities rather than assuming every asset belongs to the same party.
Assign a handover owner inside the company. That person should coordinate the departing and incoming providers without allowing an unresolved dispute to break customer-facing services.
Export the meaning of the data with the rows
Preserve field names, definitions, date bases, time zones and transformation rules. A spreadsheet containing source, status and revenue is incomplete if the next team cannot tell whether those fields mean first interaction, booked work or completed work.
Google Analytics uses distinct user, session and event scopes. Supermove milestone reports distinguish creation, booking and job timing. Include those definitions when preserving reports so the incoming team does not compare unlike measures. [1] [2]
Retain changes that affect trend interpretation
Record major tracking changes, campaign restructures, service launches and known data gaps. The next team needs to know when a conversion definition changed or a form failed, not just see a line chart with unexplained movement.
The CRM source dictionary is one important part of that documentation.
Choose the minimum appropriate customer export
Define the business purpose and authorized recipients before exporting personal information. FTC guidance emphasizes knowing what data is held, keeping only what is needed and controlling access. A full CRM or recording archive should not be the default handover attachment. [3]
Use secure approved storage and transfer methods, with access limited to the people who need the records. Keep credentials and secret keys out of ordinary spreadsheets, reports and chat messages. Transfer access through the platform's supported administrative process.
Document what the departing provider will retain or delete and how that is confirmed. Preserve necessary business records without creating uncontrolled copies in several personal accounts.
Verify creative rights and operational dependencies
List approved copy, design files, photos, videos and the permissions attached to them. Copyright ownership and licenses matter; possession of a file does not automatically establish unrestricted rights to reuse it in every context. [4]
Identify dependencies that could stop working when a subscription or agency account is removed: phone forwarding, form endpoints, automation services, reporting connectors or licensed media. Test the replacement path before removing the existing one.
Keep a controlled inventory of integration owners and required access, without embedding secrets in it. The receiving team should know how to obtain authorized credentials and who can revoke them later.
Test exports before accepting the handover
Scroll the table horizontally to compare all columns.
| Check | What to verify | Failure to catch |
|---|---|---|
| Completeness | Expected periods and record counts | Missing months or filtered rows |
| Usability | Files open and fields retain meaning | Broken encoding or opaque labels |
| Relationships | Stable IDs link inquiries and jobs | Unjoinable tables |
| Configuration | Current definitions match documentation | Historical settings mistaken for active ones |
| Recovery | Authorized team can restore or use key assets | An archive that cannot support continuity |
Select a small representative sample and trace it from source to report. Protect personal details during the review. A successful download is not evidence that the export is complete or useful.
Record unresolved gaps and who will resolve them. Do not sign off on a handover solely because a folder contains many files. The important question is whether the business can continue operating and explain its measurement.
Change access in a planned sequence
Agree on the cutover date, responsible people and rollback steps. Verify incoming access and critical customer paths before removing permissions that support them. Afterward, remove unneeded access and rotate relevant secrets through approved systems.
Monitor calls, forms, campaign delivery and reporting during the transition. Keep the first review focused on continuity and measurement integrity before judging the new provider's performance against a changed baseline.
The marketing systems guide helps map ownership. A tracking review can identify fragile dependencies before the transition.
Common questions
Is a dashboard export enough when changing agencies?
Usually not. Preserve underlying definitions, relevant records, account access and configuration context so the next team can reconcile and continue the reporting.
Should all credentials go into the handover spreadsheet?
No. Document owners and access procedures, then transfer permissions or secrets through approved secure mechanisms. Ordinary handover files should not expose credentials.
Your next step
Preserve control, usable data and context before changing access. Verify the handover with real acceptance checks and protect customer-facing continuity throughout the transition.
Sources & editorial notes
Platform claims cite the documents below. Operating frameworks and labeled examples are MoverFuel editorial analysis, not client results or industry benchmarks.
- Google Analytics: scopes of traffic-source dimensionsGoogle Analytics acquisition scopes have distinct meanings that should accompany exported reports. Reviewed .
- Supermove: Marketing Milestones SummarySupermove milestone date/event definitions affect report interpretation. Reviewed .
- FTC: protecting personal informationFTC guidance supports data minimization, secure handling and controlled access during transfers. Reviewed .
- US Copyright Office: What is Copyright?Copyright ownership and licensing affect reuse; possession alone does not grant every usage right. Reviewed .
