List the sources before treating them as one archive
Start with the storage you already know: a working PDM or PLM system, an older project server, inherited media or existing backups. Distinguish sources used in current operations from those holding historical projects. A backup is a known source, not proof that a complete, readable project can be restored from it.
System names and known versions help frame later technical questions. Where that information is missing, record it as unknown. An initial conversation should not require a new software purchase, system implementation or speculative recovery exercise.
| Source | Useful information to collect | Question for a later review |
|---|---|---|
Current PDM or PLM |
Responsible team, known version and historical project groups |
Which records and relationships remain accessible? |
Project server |
CAD systems, folder groups and approximate periods |
Where are the referenced parts and drawings? |
Inherited collection |
Broad origin and people who understand it |
What permissions and system dependencies apply? |
Legacy backup |
Type of source and available technical support |
Can it be restored, and is doing so authorised? |
References matter as much as individual files
An assembly may refer to many component files, and a drawing may belong to a particular model revision. Libraries, external references and associated BOMs can be part of the same engineering context. Exporting one isolated file does not establish that those relationships will still be understandable.
Functions such as SOLIDWORKS Pack and Go illustrate that a design set can span several connected files. This is an example of a relationship to consider, not a universal export instruction. The appropriate method depends on the system version, the records and the scope eventually agreed.
Separate access, readability and permission
An available login indicates that someone can access a system. It does not establish that every document may be licensed for another purpose. Similarly, being able to view a drawing does not prove that its complete source model is available.
Record known gaps rather than trying to repair them before the first conversation: an unavailable library, an uncertain version, a possibly incomplete assembly or an inherited collection with unclear origins. Design-file provenance and the archive counting guide address those questions separately.
Identify responsibilities before a system is retired
Later steps may need input from the technical administrator, the design team and whoever can approve disclosure. Initially, give us your role rather than anyone's personal login details. Passwords, server addresses and project links do not belong in the enquiry.
If a system or service-provider contract is ending, describe the affected source and the known timing. Decisions must still respect existing access arrangements and protection requirements. Do not keep an obsolete system running, or rebuild it, solely on the assumption that licensing will follow.
Prepare a useful next decision
The overview should identify a manageable collection and your current level of knowledge. If a sample becomes useful, representative projects and their necessary references are scoped separately. Recipients, protection arrangements and required agreements are established before transfer.
The licensing process explains how this system map can support the next conversation without requiring source files at the outset.