AutoCAD Cloud Collaboration for Engineering Firms: What Works and What Breaks

Most engineering firms didn’t choose their cloud setup. It happened. Someone started a project in a OneDrive folder during a busy month, a consultant sent a Dropbox link, and now drawings live in four places and nobody is sure which xref is current. If that sounds familiar, this guide is for you. It’s written for principals and office managers at Ontario engineering firms of roughly 15 to 100 people, and it sits alongside our broader guide to IT for engineering firms.

I’m Jeffrey Bowles, Partner and Director of IT Services at ACT360. Below I’ll walk through the 4 realistic ways to collaborate on AutoCAD files in the cloud, where each one breaks, how to keep references intact, and how to pick the right one for your firm.

AutoCAD cloud collaboration means more than one person working on the same drawings without sharing an office file server. The drawings either sync to each person’s computer, live in Autodesk’s own cloud storage, or stay in one place while people connect to them remotely.

Those are very different things, and the word “cloud” hides the difference. In practice, firms end up with one of 4 setups.

1. A general sync folder. OneDrive, SharePoint, Dropbox, Box or Google Drive, with files synced to each designer’s laptop.
2. Autodesk’s cloud project storage. Autodesk Docs, reached from File Explorer through Autodesk’s Desktop Connector.
3. Files stay put, people connect in. Remote desktop into an office workstation, or a cloud-hosted desktop sitting next to the files.
4. Review without editing. Sharing a drawing for comments and markups instead of handing over the file.

Most firms need a mix. Live project work goes in one place, and client or consultant review happens another way.

Because AutoCAD works on a local copy and the sync client decides when that copy reaches the cloud. Autodesk says plainly that sync timing is handled by the third-party client and isn’t under AutoCAD’s control.

Autodesk’s own help page, About Using Cloud Storage for Drawings, explains what happens underneath. AutoCAD supports OneDrive, Dropbox, Box and Google Drive, but every one of them works through a local cache on each computer. With OneDrive, your changes only exist on your own machine until you close the drawing. If 2 people save the same file, the provider picks a winner and saves the other person’s work as a separate “conflicted copy”.

On a 3-person job with simple drawings, you might never notice. On a project with a dozen xrefs and designers in the office and at home, the cracks show quickly.

• Stale references. A designer opens a sheet whose xref hasn’t synced yet and coordinates against last week’s base plan.
• Duplicate files. Conflicted copies pile up, and someone has to work out which one is real.
• Broken paths. Sync folders sit under each user’s profile, so a full path on one laptop doesn’t exist on another.
• Files that aren’t really there. Files-on-demand settings leave a placeholder on disk until the file downloads, which can trip up references.

Here’s my honest take. Sync folders are good for sharing finished PDFs, issued drawings and reference material. They’re the wrong foundation for live, heavily referenced AutoCAD work. If your firm already lives in Microsoft 365, our guide to getting more from OneDrive and Teams covers where they shine.

Match the setup to file size, team spread and how often you exchange drawings with outside firms. Remote access to centrally stored files suits most small offices. Autodesk’s cloud storage suits firms sharing live drawings with partners.

The first row is the default in many small offices because it was easy to set up, and it’s usually the slowest way to work on CAD from home. We cover the remote options in more depth on our CAD IT support page.

Keep every project in one folder structure, use relative paths for references, and move or send drawings with their references as a package. A lot of broken xrefs come from absolute paths that only exist on one person’s computer.

A few habits prevent most of the pain.

1. One project root. Drawings, xrefs, images and standards for a project live under one top-level folder, not scattered across personal folders.
2. Relative paths. References point to files relative to the drawing, so the project still works when the folder is opened from a different computer or drive letter.
3. Packages for outside parties. When drawings go to a consultant, Autodesk recommends eTransmit, which bundles a drawing with all its referenced files.
4. Upload with references. When moving drawings into Autodesk’s cloud storage, Desktop Connector can gather referenced files and flag missing ones before the upload goes ahead.
5. Keep BAK files on. Autodesk recommends keeping AutoCAD’s backup files even in cloud storage, because provider version history is limited.

None of this is exciting. It’s also the difference between a project folder you can move in an afternoon and one that takes a week of re-pathing.

Give reviewers a way to comment without editing your working files. Markups on a shared view or a PDF set keep your drawings clean, and you decide what gets changed.

AutoCAD’s Trace feature was built for this. Autodesk describes it as a safe space to give feedback without altering the existing drawing. A reviewer marks up on top, and the designer decides what to copy into the drawing. Traces work in drawing formats from 2010 onward and not in DXF, so check what format you’re sharing.

For clients who don’t use AutoCAD at all, a marked-up PDF set is still the most practical route. What you want to avoid is the email thread with 6 attachments and 3 versions of the same sheet. If design reviews are a constant headache, a simple client portal can pull feedback and approvals into one place, which is the kind of tool our custom web applications team builds.

It matters when a client contract or public-sector project asks where project data is held. Autodesk now lets firms choose Canada as the primary storage region for select cloud products, but the region is set when the account hub is created.

In June 2025, Autodesk announced Canada as a data storage region for products including Autodesk Docs and BIM Collaborate. Autodesk’s regional offerings FAQ adds 2 details worth knowing before you set anything up.

• You can’t move a whole project between regions later. Files can be copied with a replication tool, but versions, markups and permissions don’t come along.
• Identity data stays in the US. Account and hub data continue to be stored and processed there, even when project files are in Canada.

So if Canadian storage matters to your clients, decide that first. It’s much easier to get right on day one than to fix after 2 years of projects.

No. Sync faithfully copies mistakes, deletions and encrypted files to every connected computer. You still need separate, versioned backups that can be restored, and someone who has actually tested a restore.

Provider version history helps with an accidental overwrite, but Autodesk itself notes that histories are often kept for around 30 days and that personal Box accounts don’t keep versions at all. That isn’t enough for a project that runs 18 months.

The basics we put in place for engineering clients are simple.

• MFA on every account that can reach project files, including Autodesk and Microsoft accounts.
• Sharing links that expire, and a check of external access when a project closes.
• Access removed the day someone leaves, with their licence reassigned.
• A backup copy kept outside the sync relationship, with restores tested on a schedule.

More on how that works is on our business continuity and disaster recovery page and our cybersecurity services page.

Answer these 6 questions before you move a single project folder. Together they point to the right setup for most engineering firms between 15 and 100 people.

1. How big are your typical drawings and how many xrefs do they carry? Heavy, highly referenced sets favour keeping files in one place.
2. Where do your people work? One office with occasional home days is a different problem from 3 offices and a mostly remote team.
3. How often do outside firms edit your drawings? Frequent live exchange with consultants points toward Autodesk’s cloud storage.
4. Do any clients ask where data is stored? If so, settle the storage region before you set up the account.
5. Which AutoCAD releases are in use? Mixed releases cause their own problems, cloud or not.
6. Who will own the folder rules? Every setup decays without someone keeping the structure clean.

We look before we recommend. Through the Assess and Comprehend steps of our ACTION approach, we check file sizes, where projects live today, how drawings move between staff, offices and consultants, and what your clients require. Sometimes the answer is a cloud platform. Often it’s a better remote setup around the files you already have, and a cleanup of the folder structure.

When we moved a law firm off a vendor-locked remote desktop setup to Microsoft Azure, the goal was the same one we bring to CAD work, putting the work where it runs fast and stays under the firm’s control. That story is in our law firm Azure migration case study, and our cloud migration page explains how a phased move works.

The firms that get AutoCAD cloud collaboration right don’t start with a product. They start with where their drawings are, how references are built and who needs to touch them, then pick the simplest setup that keeps files in one trustworthy place. Get that right and the cloud becomes boring, which is exactly what you want.

If you’d like a second opinion on your setup, our free IT Readiness Assessment looks at how your team works with drawings today and gives you a short list of what to fix first. For budgeting, see IT support costs for engineering firms. You can also call 705-739-2281 or email [email protected].