Copyright © 2026 Everyday Backups · everydaybackups.com · Secure cloud backup for small business & personal files
An agency's business runs on files that belong, in large part, to someone else. Client brand assets, campaign deliverables, source files, contracts, and retainer agreements represent not just the agency's operational history but its clients' intellectual property and trust. A single Windows workstation or a shared network drive holds most of it. The question every agency principal needs to answer honestly is whether they could retrieve any client's files, on any day a drive fails or ransomware hits, and whether the copy they retrieve is current and intact.
Everyday Backups provides managed, encrypted cloud backup for Windows computers, with monitoring, restore support, and monthly backup health reporting. Paid plans from $5.99/mo.
An agency's file library grows engagement by engagement across the life of every client relationship. Project files, brand assets, and deliverables accumulate across workstations, shared drives, and the machines where production work actually happens. The categories below are what a working agency should be able to retrieve, for a specific client and project, on demand.
A gap in any one of these categories becomes the critical problem in a specific situation: when a client calls to reactivate a campaign from two years ago and expects you to have the source files, when a contract dispute requires retrieving the exact signed SOW, or when the workstation holding five years of client brand assets develops a failed drive over a long weekend.
Most agencies already know their files matter. The practical difference for a creative or marketing agency, compared to most other small businesses, is that a significant portion of the data at risk is client-owned. Losing it does not just disrupt internal operations. It breaks client trust and can undermine the agency's contractual obligations.
Clients submit brand assets, raw photography, product media, and reference files trusting that the agency will handle them responsibly. Many clients no longer maintain their own complete archive of files they have passed to the agency, particularly for assets built or curated specifically for the engagement. When those files are lost, the client faces the cost and disruption of recreating materials they believed were in safe hands, and the agency faces a conversation about how that happened.
The same dynamic applies to deliverable source files. A client who wants to take work in-house at the end of a retainer, bring on a new agency, or simply modify a campaign asset expects the source files to be available. If the working PSD, AI, or video project file behind a deliverable is gone, the client cannot make changes without starting from scratch. That is not a technical inconvenience. It is a failure of stewardship over files the client reasonably expected to be recoverable.
Approved emails, signed contracts, and communication threads carry their own weight. Email is routinely the approval record for creative direction, copy changes, and scope expansions. A PST archive or local mail store that is lost in a drive failure takes with it documented evidence of what was approved and when. For a disputed invoice or a scope disagreement, that record is not replaceable from memory.
This is the core reason agency backup deserves deliberate attention: the files at risk are not just the agency's operational data. They are the agency's custodianship of its clients' creative and business assets.
The 3-2-1 rule is a backup framework recommended by CISA and cited in small-business backup guidance. For an agency managing client files, brand assets, and deliverables across multiple Windows machines, here is what it looks like applied to the files that actually keep the business running.
The working copy on your design or production workstation is one. A local external drive or network-attached storage holding a copy is a second. A third copy, off-site in encrypted cloud backup, is the one that survives a local event affecting both of the first two at the same time, whether that is a fire, a theft, or ransomware encrypting every drive the machine can reach. Each client's assets and deliverable source files should exist in all three places before the originals are at risk from a single failure.
Keeping two copies on the same type of drive in the same location does not provide meaningful redundancy against a hardware failure or an event affecting the building. CISA guidance calls for at least two different storage media types, for example an internal or external local drive and a separate off-site cloud destination, as distinct and independent layers of protection rather than two copies in the same physical space.
Off-site means physically separated from the agency's office. Cloud backup satisfies this requirement when data is stored in a remote data center rather than on a drive in the same building. The off-site copy is the one that protects you when everything at the office is affected at once: a flood, a break-in over the weekend, or ransomware that encrypts the workstation and every USB drive connected to it.
A practical workflow looks like this: client files arrive and are saved to the project folder on the workstation, the backup system picks them up and sends them to the off-site destination automatically, and the local copy on an external drive or network storage gives you a fast-restore option for active projects. All three copies exist without manual steps on each project day. Older client archives remain in backup scope so files can be retrieved on any reactivation request without hunting through disconnected drives.
The questions below are a starting framework for evaluating your current file storage and backup arrangement. Working through them honestly is the fastest way to identify whether you have genuine redundancy or a setup with gaps that are not yet visible because nothing has gone wrong yet.
For a broader self-assessment covering your overall backup posture, take the small-business backup checklist.
The three most commonly overlooked backup targets in a marketing or creative agency are deliverable source files, local email archives, and the accounting file. Understanding what these hold and where they are stored is essential to confirming that your backup scope is actually complete and not just covering the exported deliverables and top-level project folders.
Every deliverable an agency produces, a finished ad, a print layout, a video, a web graphic, exists in two forms: the exported final file that was delivered to the client, and the editable source file that produced it. The exported version is what the client received. The source file is what the agency needs in order to make changes, produce new sizes or formats, or hand off the work to a new provider.
Agencies often back up exported deliverables more reliably than source files, because deliverables live in a structured output folder while source files live in layered working directories that can be large and sometimes scattered across more than one location. But if a client wants to modify a campaign, expand into a new format, or simply take ownership of their creative assets at the end of a retainer, it is the source file they need. An exported JPEG or flattened PDF cannot be edited back into a layered original.
Confirming that your backup scope explicitly includes the directories where your design and editing software stores its working and project files, not just the export output folders, is the step that closes this gap.
On Windows machines configured with a local mail client, the mail data store, whether a PST file or an application-specific database, is often stored in a location outside the main document directories that most backup configurations are built around. It is common for this location to be in an application data folder under the user profile rather than in the Documents or project folder hierarchy.
The communication record inside that archive is not recoverable from the mail server if the server does not retain messages or if the retention window has passed. For an agency, that record includes client approvals given over email, creative direction received in threads, scope-change discussions, and any correspondence that documents what was agreed to and when. In a dispute over deliverables, an invoice, or scope, that thread is evidence. Once the drive fails and the archive is gone, the record is gone with it.
Locating the specific folder path where your mail application stores its data on each Windows machine and adding that path explicitly to your backup configuration is a one-time step. Once it is in scope, the communication record is covered alongside the project files that the correspondence refers to.
The accounting file for the agency, whether maintained in QuickBooks or a comparable tool, is often stored on a specific machine and is not always included in backup configurations focused primarily on creative project files. The file represents the complete financial record of the business: client billing history, contractor and vendor payments, operating expenses, and revenue across the life of the agency.
Intuit's own guidance recommends maintaining a backup copy of QuickBooks company files separate from the primary working location. A drive failure on the machine where the accounting file lives without a current backup means reconstructing financial records from bank statements, invoices, and any partial records that were exported or stored elsewhere, which is time-consuming and may produce an incomplete picture.
Adding the accounting file location and any associated financial record directories to your backup scope, alongside creative project folders, ensures that the business's financial record is protected with the same rigor as the creative work that generates it.
Marketing and creative agencies share a class of backup risk with other file-dependent creative service businesses, but with one key distinction: the files at risk span client-owned creative assets, the agency's own business records, and the communication threads that document the relationship between the two.
A photography studio also manages large files for clients and faces similar risks from single-drive storage and ransomware exposure. See photography studio backup for a parallel look at how those risks apply to a studio workflow. The core backup principles, 3 copies, 2 media types, 1 off-site, apply equally, and many of the gaps that appear in a photography studio setup appear in agency environments for the same reasons: large files on secondary drives, sync folders treated as backup, and no tested restore process.
A print or sign shop faces some overlapping risks around production source files and client-supplied artwork. See print and sign shop backup for a breakdown of that environment. The key distinction for an agency is the breadth of file types at risk and the client-ownership dimension. An agency is not just managing its own creative output. It is the custodian of client brand assets, client-supplied materials, and the full record of what was agreed to, delivered, and approved across every engagement.
A shared cloud sync folder gives the team access to the current state of files from multiple locations and devices. But sync is not backup. When a file is deleted by any team member, the deletion propagates to everyone's synced copy. When ransomware encrypts the working folder on a connected Windows machine, those encrypted files overwrite the synced versions. Sync does not maintain version history that lets you retrieve a file as it existed before it was deleted or encrypted. Most sync services offer some version history, but it is typically limited in depth and is not designed as a recovery mechanism for serious data loss events. Point-in-time backup with version history is what provides that protection. Sync and backup serve different purposes and should not be treated as equivalent.
An external hard drive is a useful local copy and much better than keeping client files only on the main workstation. But a single external drive is one point of failure. Drives fail without warning. A drive sitting next to the workstation can be stolen in the same break-in, damaged in the same flood, or encrypted in the same ransomware attack that hits the connected Windows machine. It is not off-site, so any event at the physical location affects it at the same time as the workstation it backs up. A single external drive is a valuable part of a multi-copy strategy, but it does not by itself cover the range of risks a working agency faces.
Agencies hold client files in the normal course of delivering work. Whether your contracts address data retention and file custody explicitly or not, clients generally expect to be able to request their files, particularly source files and approved deliverables, at any point during and after the engagement. If those files are lost because the agency's workstation was not backed up, the client faces the cost of recreating work they believed was in safe hands. The practical impact on the client relationship and the agency's reputation is the same regardless of how the contract reads. Treating client-owned files as a backup priority, not just a storage convenience, is part of responsible agency operations.
Web access to your email account confirms that the mail server currently holds your messages. It does not protect you from account deletion, provider-side data loss, or a mail client configured to download and remove messages from the server after syncing to the local machine. If your Windows mail client is set to store messages locally and remove them from the server, web access will not retrieve the locally stored messages after a drive failure. Even if messages remain on the server, server-side retention policies vary by provider and plan, and older messages may be purged outside your control. A local mail archive or PST file included in your backup scope gives you a durable copy of the communication record independent of the server's current state.
There is no universal answer, and this is a business decision rather than a technical one. Clients who have engaged the agency before often expect files to be available for reactivation, modification, or transfer at any point during or after the retainer. The practical minimum for most agencies is to retain client source files and deliverables for at least as long as the client relationship is active. Older projects can be moved to archive storage, but they should remain in backup scope rather than being removed from coverage as drives fill. The cost of storing older project files in backup is generally small compared to the cost of the conversation when a client asks for files that no longer exist.
Paid plans start at $5.99/mo. Agencies working with video, large media libraries, and deep project archives often manage significant data volumes. The right plan depends on the amount of data you need covered across all the machines and locations where client and business files actually live. The best starting point is to take the free 2-minute self-check, which will give you a clearer picture of your current posture and what a covered setup would look like for your agency.
Everyday Backups is a backup service, not legal, regulatory, or compliance advice. It does not by itself satisfy any contract-retention requirement, record-keeping obligation, or any other legal or regulatory obligation applicable to your business. No compatibility with any specific design application, video editing application, project-management tool, accounting application, mail client, or other application is guaranteed or implied; verify backup scope and file coverage with your own review. References to file types, application categories, and agency workflows on this page are for illustrative purposes only and do not constitute endorsement of or claimed compatibility with any specific software vendor or product. References to CISA documentation and FTC guidance are for informational context only and do not constitute endorsement by those organizations. Consult qualified legal and IT advisors for requirements specific to your business.
Everyday Backups runs on Windows, iPhone, iPad, and Android. Set it once; it backs up automatically, encrypted, off-site. Paid plans from $5.99/mo.
Prefer to talk to a person? Call 850-980-3691
Want a second set of eyes? Schedule your free 15-minute Backup Risk Check with our team
Copyright © 2026 Everyday Backups · everydaybackups.com · Secure cloud backup for small business & personal files