# BIM 360 to ACC migration: issues and RFI history

Canonical: https://refer.sourcex.si/systems/bim-360-to-acc-migration-data
Last updated: 2026-11-03

The BIM 360 to Autodesk Construction Cloud migration is a good moment to ask which issue, RFI and coordination histories a firm will keep. Consultants can screen for project depth and ownership, then introduce qualifying firms to SourceX without ever opening project files.

## Why is the BIM 360 to Autodesk Construction Cloud move a records moment?

The move from BIM 360 to Autodesk Construction Cloud (ACC) is a natural point to decide what project history to preserve, because issues, RFIs, submittals and coordination records can be reorganized, archived or left behind during a migration. For a construction-tech consultant, this is a planning conversation you may already be having.

Those records matter beyond construction. Issue and RFI threads show how problems were raised, routed, answered and closed, with dates, owners and attachments. They are task-oriented, outcome-labeled workflow records, which AI developers value.

This page asks you to do one thing: recognize a contractor, engineer or design firm with a deep project history and make an introduction. You never export, open or describe project files.

## What do these platforms hold?

| Record | What it contains | Why it can matter |
|---|---|---|
| Issues | Description, assignee, status, due date, comments | Problem-to-resolution trail |
| RFIs | Question, responses, cost or schedule impact notes | Structured decision records |
| Submittals | Review cycles and approvals | Multi-step approval workflows |
| Meeting minutes and markups | Coordination discussion and annotations | Context across disciplines |
| Model and drawing versions | Sheet sets, revisions | Large files; scoped separately |
| Project admin | Member roles, folder permissions | Needed to judge who owns what |

How much of this survives a migration depends on the migration path, the project settings and what the company archives. Do not promise any specific outcome; ask the project executive or BIM manager.

## Who owns project records on a construction job?

Ownership on a construction project often depends on the contract. Owners, general contractors, subcontractors and design teams all contribute to the same project environment, and the agreement may give the owner rights to project documents or impose confidentiality.

So the first question is not how much data there is, but whose it is. Start with the contractor or design firm's own operations: internal coordination, estimating, preconstruction, safety and quality programs, and projects where the contract leaves the firm with the rights. For anything else, written consent from the project owner is the safe route.

This is general information, not legal, tax or financial advice. Contract terms and state law vary, so the company should confirm with its own counsel.

## Which firms are worth raising it with?

Use the **project-depth screen**: Volume, Variety, Years, Authority.

- [ ] **Volume:** many completed projects, not a handful of large ones.
- [ ] **Variety:** several project types and delivery methods.
- [ ] **Years:** BIM 360 or earlier tools used for several years, with closed projects still accessible.
- [ ] **Authority:** a principal, CEO, CFO or authorized representative can decide on the license.

And the baseline from [who qualifies](/who-qualifies): a company in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE or Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) with 50+ full-time employees at peak (contractors excluded), several years of documented operations, and rights to the records.

Construction firms usually have other systems that add context, such as accounting and job costing in [Sage 300 CRE or Viewpoint](/systems/sage-300-cre-data-export), engineering issues in [Linear](/systems/linear-export-issues) at software-heavy design firms, or ticketing in [MSP records](/data-types/msp-ticket-data) at their IT provider.

## How should a consultant time the conversation?

| Stage | What is happening | What to do |
|---|---|---|
| Migration planning | Choosing which projects move | Ask what stays in the old hub |
| Before archiving | Closed projects are being zipped or retired | Note years and counts |
| Hub decommission | Old environment will be turned off | Raise early; deleted history is gone |
| Post-migration review | Gaps are discovered | Ask where the archive now lives |
| Strategic planning | Leadership explores new revenue options | Mention licensing as one option |

Keep metadata only. A list of projects by year, type and rough record counts is all you need, and the [data inventory builder](/tools/data-inventory-builder) gives you a place to write it down.

## What to say

> "As you move projects into ACC, you will decide which history to keep. Some firms license their own project records to SourceX. You keep ownership, choose the scope and sign only if you agree the terms. If that is interesting, I can introduce you to SourceX. I would not need to see any project files."

[Management consultants](/for/management-consultants) who advise construction clients can use this as a conversation starter during technology planning.

## How are rewards handled?

Partners earn the greater of $50,000 plus 5% and 15% of the compensation SourceX actually pays the company you refer, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. A signed agreement or a meeting alone does not trigger payment. If you consult for the firm, disclose the arrangement and check your engagement terms. See the [program terms](/terms). The [Xero records guide](/guides/keep-records-on-xero-after-business-ceases) shows how to handle a closing business.

## When to skip it

- The firm is below the 50+ full-time employees at peak baseline.
- Records belong mostly to project owners who will not consent.
- The old hub was already deleted with no archive.
- Project files are mainly drawings and models with no issue or RFI record.
- The principal will not consider an exclusive license.

## Common mistakes when screening a construction firm

| Mistake | Why it hurts | Fix |
|---|---|---|
| Counting active projects only | Closed-project history is the valuable part | Ask about completed jobs by year |
| Assuming the contractor owns everything | Owner contracts may restrict use | Review contract language with counsel |
| Asking for a project export to look at | Moves confidential files around | Ask for counts, years and project types |
| Waiting for hub shutdown | Deleted history cannot be licensed | Raise it during migration planning |

## Next step

When a firm has deep project history and a decision-maker, [register as a partner](/register) and submit the introduction. Companies can also apply directly at [sourcex.si/apply](https://sourcex.si/apply).
