Archicad project recovery

A damaged Archicad PLN may have a usable BPN backup, autosave database, or archived PLA.

Archicad projects can fail after crashes, interrupted transfers, cloud synchronization, storage faults, or version problems. Solo and Teamwork projects use different recovery sources.

Understand the symptom

BPN is the previous saved project; autosave can contain newer unsaved work.

WHY

What is happening

When backup creation is enabled, Archicad keeps a BPN beside the project. Crash recovery may use local database files, while Teamwork relies on local data and BIMcloud state. These sources represent different times and should be compared rather than substituted blindly.

What you may see

Symptoms that change the recovery path.

01

Cannot read plan file

The PLN may be corrupt, incomplete, incompatible, or damaged during transfer.

02

Unknown document version 0.0

Header or file content may be missing or truncated.

03

No recovery prompt after crash

Autosave data may be absent, stale, or stored in another local-data folder.

04

Project opens with missing libraries

The model database survived but objects and links do not resolve.

Protect the source

Actions that can make the situation worse.

01

Opening and saving in a newer version changes compatibility

Test upgrades only on copies.

02

Cloud sync can replace package generations

Pause it before comparing PLN and BPN files.

03

BIMcloud actions affect shared state

Do not re-share or overwrite a Teamwork project during recovery.

Do this now

Safe steps before evaluation.

01

Copy PLN, BPN, PLA, and autosave data

Keep original filenames, timestamps, and folder structure.

02

Preserve libraries and hotlinks

Collect embedded libraries, linked modules, drawings, and external assets.

03

Record solo or Teamwork context

Note Archicad build, BIMcloud server, last send/receive, and crash sequence.

04

Protect the project volume

Image storage first if files produce I/O errors or copy failures.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Project-generation map

NEPFOSYS compares PLN, BPN, autosave, PLA, local data, and shared-state evidence.

02

Copy-based recovery

Candidates are opened in compatible versions without overwriting sources or Teamwork state.

03

BIM validation

Stories, elements, attributes, views, layouts, libraries, links, and priority sheets are reviewed.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

What is an Archicad BPN file?

It is a backup of the previously saved project when Make Backup Copy was enabled.

Is BPN always newer than autosave?

No. BPN and autosave represent different save events; compare their timestamps and contents on copies.

Can a Teamwork project be recovered like a solo PLN?

Not necessarily. Local data, send/receive history, and BIMcloud backups must be considered together.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case