A transfer copies training content, such as programs, workouts, blocks and metrics, out of one institution and into another, so your library can move with you when you change organizations or share it with another one. This article covers who can start a transfer, what goes in it, the two approvals, and where the content ends up.
How a transfer works
A transfer has two legs, and each can need a manager's sign-off:
Export. You pick content from a source institution. A manager there approves it leaving, and FYTT clones it into a package: a new, private institution only you can see, on a trial.
Import. You choose a destination institution that has invited you. A manager there approves it arriving, and FYTT moves everything from the package into the destination. The package institution is then deleted.
The original content in the source institution is never changed or removed. Every step shows on the transfer's page, on a rail that reads Setup, Select, Review, Source approval, Package, Destination, Target approval and Landed.
Who can start a transfer
Open transfers from the avatar menu in the top bar: click Transfers (1). You see it if you're a manager of an institution, or a Coach or Trainer on one of its teams (see Staff access), or if you've started a transfer before.
The Transfers page lists the transfers you started, with their Status, Source and Destination. Click a row (2) to open it. Transfers you're asked to approve aren't listed here; you reach those from the email FYTT sends you.
Starting a transfer
On the Transfers page, click New transfer (1).
Enter a Transfer name (1). Only you and the approver see it.
Pick the Source institution (2), the one the content leaves from.
Pick the Approving manager (3), a manager at the source institution. If you're the only manager there, the panel says No sign-off needed instead, and the export skips source approval.
Optionally, click Add a note for the approver to explain what the transfer is for.
Click Start export (4).
FYTT opens the builder, where you pick what goes in the package.
Choosing content
The builder lists twelve content types in three groups:
Programming: Programs, Progressions, Workouts, Blocks and Exercises
Analysis: Metrics, Leaderboards, Group reports and Athlete reports
Organization: Groups, Teams and Automations
Tick the items you want, or use Select all and Clear, which act on everything the search matches.
FYTT adds whatever your picks depend on, and marks those rows Auto. A program brings its workouts, blocks and exercises; anything that records or reads a metric brings that metric; content assigned to a group or owned by a team brings the group or team; an automation brings the programs it assigns. An auto-included item can't be removed on its own: deselect whatever needs it.
When you're done, click Review & submit. The review shows a Manifest with the count of each type, and the Intellectual property & athlete privacy representations you're agreeing to. Click Submit for approval, tick the agreement, and confirm.
Transfers move content, not athletes Athletes, roster membership and training history never travel with a transfer. Logged workouts, results, injuries and notes stay in the source institution. A transferred team arrives with its settings and groups, but no athletes.
The approvals
Each approver gets an email with a link to the request. The approval page shows the same manifest and history you see, with a Your decision panel: choose Approve this request or Deny this request (1), add Comments (2), and click Submit decision (3). The requester is emailed either way, and the comment travels with the decision.
Source approval is given by a manager of the source institution, other than you.
Target approval is given by a manager of the destination institution, other than you. You can't approve your own import, even if you manage the destination.
Landing the content
When the package is built, the transfer shows Package ready and two paths. They're mutually exclusive:
Operate from the package: click Go to the package institution and coach from it as a new, independent institution. Once the trial ends you'll need a plan.
Import into another institution: click Start an import, pick the Destination institution and its Approving manager, and click Request import. Only institutions that have invited you are listed. If there are none, ask the destination to invite your FYTT email address, then come back.
An import deletes the package When an import completes, the package institution and everything in it are permanently deleted. The content lives only in the destination from then on.
In the destination, programs, progressions, workouts, blocks, exercises and metrics belong to the institution, so they appear in the library of every team there (see Training library). Content from your personal library stays personal if you're on staff at the destination. Transferred teams become teams of the destination. Workouts and blocks whose names are already taken there get [imported] added to the name. To schedule the programs for athletes, add them to a plan (see Plans and Programs).
When the transfer is finished, its page shows Transfer complete and a Go to button for the destination (1).
Tracking a transfer
The badge next to the transfer's name gives its status:
Draft, Awaiting source approval, Source approved, Building package, Package ready
Import draft, Awaiting target approval, Target approved, Landing content, Transfer complete
Export denied, Import denied, Export failed, Import failed
The Audit trail (2) records everything that happened, newest first: who created the transfer, who each request was sent to, reminders, withdrawals, each approval or denial with its comment, and when the content landed. It stays on the page after the transfer finishes. FYTT also emails you at each step, so you can leave a long package build running.
A transfer is stuck awaiting approval
Awaiting source approval or Awaiting target approval means the request is with a manager. The page names them and says how long it's been waiting. Click Resend email (1) to send them the request again; the reminder shows in the Audit trail (3).
To ask someone else, click Withdraw request (2). An export goes back to Draft, where Transfer settings lets you pick a different Source approver before you submit again. A withdrawn import goes back to Package ready, and you can start the import again with another approving manager.
A request was denied
A denial shows the approver's comment. For an export, your selection is kept: click Modify selection, make the changes, and resubmit to the same approver, or click Withdraw transfer to remove it. For an import, the package is untouched: click Request again, Choose a different destination, or Keep operating from the package.
A transfer failed
A failed build or landing keeps everything you selected and leaves the package intact. The page shows a Reference code: click Retry, or Contact support with that code.