How to Switch OnlyFans Agencies: A Creator Handover Checklist

Define what you want the new agency to change

Write the reason for leaving in terms you can check. “Better communication” might mean a named account lead, an agreed review schedule and an escalation contact. “More support” might mean editing help, a content calendar or coverage for a specific operating task. Ask the proposed agency to describe who will do that work and what you will need to supply.

Compare the current and proposed scopes before setting a start date. Mark each function as continuing, ending or changing hands. Include work you handle yourself. If the new agency does not provide a service the current team performs, choose who will cover it before the handover.

Review the existing agreement and any questions about notice, fees, content rights or outstanding obligations with your adviser. Resolve those questions before relying on a transition date. This checklist does not determine when you can leave or what either party owes.

• Write one observable change you expect from the next team.
• List the work you will keep, transfer or stop.

Name the people who will approve and complete the handover

Choose one person to coordinate the handover. You may hold that role yourself. The lead keeps the task list, asks for missing information and brings decisions back to you. Name a contact at the outgoing team and a contact at the incoming team, where both teams have agreed to participate.

Keep approval separate from completion. A coordinator can confirm that a file arrived; you still need to approve the planned use of your content or a change to your operating scope. Record who can approve posting, pricing, new offers and changes to your creative boundaries. Avoid leaving those decisions inside a message thread that only one team can access.

Agree where you will record updates and how to raise an urgent problem. Add a backup contact for the changeover window. If a team cannot name the person who owns a task, leave that task open and resolve the responsibility before work begins.

• Creator: approves scope, boundaries and the start of the new arrangement.
• Handover lead: tracks tasks, evidence, dates and unresolved questions.

Inventory permitted access and content

List the accounts, content folders and tools involved in the agreed work. For each, record the owner, authorized user, purpose of access and person responsible for removing access at the end of that scope. Keep passwords, recovery codes and subscriber details out of this document. An access inventory records permissions; it is not a shared credential sheet.

Check which access methods the service permits before adding anyone. Keep account recovery under the authorized owner’s control and use the service’s available permission controls. Do not assume that an agency change grants a new provider permission to use an account or receive its data. Resolve access questions with the service or an appropriate adviser.

For content, record which files the new team needs, where the owner keeps them, and the approved use. Distinguish finished assets from drafts. Have the recipient confirm that the agreed files open and match the inventory. Keep any necessary transfer within an approved secure workflow rather than attaching a whole account archive to the handover notes.

• Record the person, purpose and end date for each access permission.
• Confirm the agreed content inventory without copying private fan records into it.

Assign unfinished work before the cutover

Ask the outgoing team for a list of work that will remain open on the proposed handover date. Include scheduled posts, approved campaigns, editing requests and reporting still due. For each item, agree whether the outgoing team will finish it, the incoming team will take it over, or you will pause it.

Record the agreed owner and deadline. Use a task reference for any sensitive work; keep the underlying details in the system where the authorized person handles them. A task marked “sent” still needs the recipient to confirm that they received it and understand what remains.

Reconcile the reporting period with the teams so you can tell which work belongs to which scope. Record unresolved invoice or contract questions without presenting them as settled. Your adviser can help resolve a disagreement about obligations; a handover checklist cannot remove those obligations.

• Check scheduled activity so both teams do not perform the same action.
• Keep open items visible until the receiving owner confirms acceptance.

Set a cutover date and a stop condition

The cutover is the time the new team starts its agreed work. Choose it after checking notice questions, team availability, permitted access and the content schedule. Avoid choosing a date just because the new agency wants to begin.

Walk through a sample task before live work starts. For example, ask the incoming lead to locate an approved content asset, explain who approves its use and describe how they would escalate a missing instruction. Use a sample that does not require contacting fans or changing an account. Record any gap and assign someone to resolve it.

Define the reason you would postpone. Missing approval, uncertain access or an unassigned scheduled campaign can each justify holding the affected work. Agree who makes that call and how both teams will hear about it. Do not default to giving the outgoing team renewed access if something fails; the creator must approve any change in scope or permissions.

• Proceed when the owners, permissions and first tasks match the agreed plan.
• Pause affected work when a required approval, access check or responsible person is missing.

Check the first day and review the first week

On the first day, ask the incoming lead to confirm the tasks they have accepted. Check the next scheduled activity against your approved plan. Ask the responsible owner to confirm that expired access has ended and that the team can find the files it needs. Record the result rather than assuming that a quiet inbox means completion.

At a review during the first week, compare completed work with the handover list. Discuss missed items, duplicate activity, approval delays and any departure from your boundaries. Give unresolved issues an owner and another review date. Change the timing to suit the scope; a weekly meeting is a suggested checkpoint, not a guarantee that the transition is complete.

Separate operational evidence from business results. A team can complete the handover while revenue changes for other reasons. Use a consistent reporting period and metric definition when you review performance, and avoid judging a new arrangement from one strong or weak day.

• First day: confirm accepted tasks, scheduled activity and access changes.
• First-week review: close verified items and assign the remaining work.

Copy this handover ledger

Use one row per task in a document both authorized leads can review. Keep the row short enough that you can see who must act next. Add a link or reference to completion evidence, with access limited to the people who need it.

For a hypothetical content-calendar handover, your row could read: Task: deliver next week’s approved calendar. Current owner: outgoing account lead. Receiving owner: incoming account lead. Due: before cutover. Evidence: receiving lead confirms the calendar opens and matches the approved dates. Open issue: creator still needs to approve Friday’s asset. Status: waiting for creator approval.

That row gives you a concrete reason to keep the Friday task open while completing the rest of the transfer. Use the same format for reporting and tool access. Do not place passwords, private conversation extracts or fan contact details in the evidence column.

If you are considering FONCÉ, review our OnlyFans management scope and apply to discuss fit before committing to a change. Our published process starts with an application and private review, followed by a scope conversation when there is a fit. Agree the responsibilities and terms before planning onboarding.

• Task and approved scope
• Current owner and receiving owner
• Due date and required approval
• Completion evidence and open issue
• Status and next review date