How to switch design agencies mid-project without losing your work

Quick answer: To switch design agencies mid-project, read your contract first, then get every source file, library, and account moved into workspaces you own before you give notice. Exit at a milestone, not mid-sprint, run a short overlap so the new team hears the reasoning behind open decisions, and start the new team on one small task.

Switching design agencies halfway through a project feels risky because it is. Most of the risk has nothing to do with the new team's talent. It comes from what gets lost in between: files sitting in someone else's account, half-made decisions with no written reason, and a few weeks where nobody owns the work.

The good news is that almost all of it is preventable. The order you do things in matters more than how fast you move.

Signs it is time to switch

Every engagement has a rough week. A pattern is different. These are the signals worth acting on:

• Deadlines slip repeatedly and the reasons change each time.
• You rewrite briefs because the work keeps missing the point, not because your priorities moved.
• Nobody on their side pushes back on a weak idea or asks why a feature matters.
• Updates arrive as finished screens with no reasoning, so you cannot tell what was considered.
• Your engineers keep asking questions the files should already answer.

If two or three of these sound familiar, have one direct conversation first. Name the problem, say what good looks like, and give it two weeks. Sometimes that fixes it. If it does not, you have your answer, and you have a written record that you tried.

Step 1: read your contract before anything else

Pull out the agreement you signed and look for four things:

• Ownership. Does it say you own the final work, the working files, or both? "Final deliverables" and "editable source files" are not the same thing, and many disputes start in that gap.
• When ownership transfers. Some contracts transfer rights only after full payment. Know whether an unpaid invoice affects what you can take with you.
• Notice and termination terms. Look for notice periods, early exit fees, and anything owed for work in progress.
• Pre-existing tools. Agencies often keep the rights to their own templates and internal tools. That is normal, but you should know what falls outside your ownership.

If the contract is silent or unclear on any of these, talk to a lawyer before you give notice, not after. This article is practical advice, not legal advice.

Step 2: secure your files and accounts quietly

Before the agency knows a change is coming, make sure everything you depend on lives somewhere you control. You are not hiding anything. You are making sure a tense conversation cannot leave you without your own product.

Design files and libraries

Exported PNGs and PDFs are not enough. You want the native files: the full Figma files, the shared component libraries, and any design tokens. Ask for them to be moved into a Figma team you own, or exported as .fig files you can open in your own workspace.

Watch out for linked libraries. If your main files pull components from a library that lives in the agency's team, moving the files alone can break those links. Move the library together with the files that use it.

Websites, code, and accounts

List every account the agency set up or manages: the website builder, hosting, domain registrar, analytics, repositories, stock and font licenses, and tools like Loom or Notion that hold project context. For each one, confirm that your company is the owner, not a guest with access.

Brand assets

Logo source files, the brand guideline, font files with their licenses, color values, and any motion or video project files. If a launch video exists, ask for the project files and the music license, not only the final export.

Step 3: map the work in progress

Make a simple list with three columns: finished, in progress, not started. For anything in progress, note where it lives, who decided what, and why. A half-finished flow with no written reasoning is often worth less than a blank page, because the new team will either redo it or guess.

This list is also the base of your handoff document. If you want a model for what a complete handoff looks like, our design handoff checklist for startups covers the files and specs engineers need, and most of it applies when work moves between studios too.

Step 4: pick the exit point and give notice

Time the exit to something concrete: the end of a sprint, an approved milestone, a delivered screen set. Cutting off mid-build leaves you with work frozen at its least useful point.

When you give notice, keep it calm and specific. Say what is ending, when, and what you need handed over. Ask for a structured handoff rather than an immediate cutoff. An agency that feels blindsided usually cooperates less. An agency that gets a clear, professional exit usually hands over a cleaner package.

A simple rule helps: tie the final payment to a completed handoff checklist. Most reasonable studios accept that, and it gives everyone a shared definition of done.

Step 5: run a short overlap

If you can, keep a few days where the outgoing and incoming teams talk directly, with you in the room. The reasoning behind design decisions rarely survives being retold secondhand. One recorded walkthrough of the files, the open questions, and the decisions still pending saves the new team days of reverse engineering.

If the relationship has broken down and an overlap is not possible, the written map from Step 3 does most of that job.

Step 6: choose the next team on what went wrong

The most common mistake is hiring the opposite of the last agency instead of fixing the actual problem. If the issue was slow turnaround, ask about delivery rhythm. If the issue was shallow thinking, ask who will challenge your product decisions and how. If the issue was ownership, read the new contract's ownership clause before anything else.

Look past the polished case studies, too. Our guide on how to evaluate a design agency's portfolio before you hire them walks through what to look for and what to ask. If you are moving to a monthly model, what to check before you sign a startup design subscription covers the terms that matter most.

If you are weighing a switch right now and want a second opinion on what to keep and what to redo, send us what you have and we will tell you where we would start.

How we set this up at Artone

Here is how our own terms handle the problems above. With us, full ownership of all files, assets, code, and Framer sites transfers to the client, and Framer sites move into the client's own account. Our NDAs run on a standard two-year term. The Retainer is cancel anytime, and if we are not a fit within the first week, we refund 75%.

That last part matters for this topic. A team you can leave cleanly is a team you can trust with work in progress. You should never feel that switching away from your design team means losing your own product.

If you bring a project to us from another team, our first week is about the list in this article: get access to the real files, understand the decisions already made, and agree on what to keep before we redesign anything. Updates then come every other business day, so you can see within the first week whether the new setup is working.

Start the new team small

Do not hand the new team the whole backlog on day one. Give them one contained task with a clear outcome, such as a single flow, a landing page section, or a cleanup of the component library. It shows you how they think, how they communicate, and how they handle your existing files, before you commit the bigger pieces.

Then build from there. If the first task lands well, expand the scope. If you are still deciding between ongoing work and a fixed project for what comes next, design retainer or one-off project breaks down how to choose.

A quick switching checklist

• Contract read: ownership, transfer timing, notice, and pre-existing tools.
• Native design files and libraries moved into a workspace you own.
• Website, domain, hosting, analytics, and repository ownership confirmed.
• Brand source files and font licenses collected.
• Work in progress mapped with the reasoning behind each decision.
• Exit timed to a milestone, with final payment tied to the handoff.
• Overlap or recorded walkthrough completed.
• New team started on one small, clear task.

Switching mid-project is uncomfortable, but staying with a team that is not working costs more every week. If you want help taking over a project without losing the work you already paid for, book a call with our team and we will walk through it with you.