The folders are the project’s memory
Years of a project’s structure sit in its folder names. A bulk copy that flattens them leaves a pile of files that only the person who made the original tree can find their way around.
Moving an archive
A project is already running, and its drawings, specifications and correspondence sit in a shared drive or another system. They have to move over with their folders intact, and nothing already in the new place may be overwritten. This page is a plan for that move in Fidrel: what to clean first, how to test with one folder, how the review step works, how to split a large archive under the limits, and what does not move with the files.
30 days free · No long-term contract.

Years of a project’s structure sit in its folder names. A bulk copy that flattens them leaves a pile of files that only the person who made the original tree can find their way around.
Once people have started uploading, a second copy of the same sheets either duplicates them or replaces something newer. The move has to know the difference between a file that is new and a file that is already there.
Number, title and revision live in file names written by dozens of people. Names with odd separators or a trailing “final” turn into odd numbers in the new register, and nobody notices until a sheet is not found.
The Import center takes a folder, a ZIP file or a CSV of folder paths. Folders are kept and merged with existing folders of the same name, so an import into a project that already has a drawings folder adds to it. Documents that already exist are skipped, or get the file as a new version, as you choose, and unchanged files are always skipped. A file whose number is taken becomes a new number rather than a duplicate, and says so in the review. Files that sat loose at the root are gathered in folders of their own, so they show in the document register.
Documents, drawings & models
An imported version keeps a trace of where it came from. Its details show the ZIP archive it was in, the Path in archive and the Checksum, and the change note carries the name of the source. Finished imports are listed under Earlier imports as Done, Done with exceptions or Failed, with the reason for each file that was skipped or failed. If you must show later where a drawing came from, this is the place to look.

Step 1
The import reads document number and title from each file name, just as a normal upload does. Fix the names that do not follow your pattern at the source, and delete system files and empty files, which the import leaves out anyway.
Step 2
Open the Import center under Administration and use Choose folder or Choose ZIP file on a single discipline. Drop it in, look at the result in Documents, and judge the numbering and folders on a small sample before the big run.
Step 3
Fidrel lists every file as New, New version or Already there before it saves anything. Choose where to Import into, skip the top folder if it only wraps the contents, and untick any file. Set If a document already exists to Skip it or Add as a new version.
Step 4
One import takes up to 5,000 files and 5 GB. Split a larger archive by discipline or by year, and run the parts one after another. Keep the page open while it runs; Stop ends it after the current files, and Retry the ones that failed picks up the rest.
Step 5
Choose Open in Documents to check the result. Imported files come in as Working. Select a group of them and use Change status; the approved statuses can be set only by an administrator or a document controller.
One import takes up to 5,000 files and 5 GB. A ZIP file can be up to 1 GB, and each file up to 50 MB, with IFC models allowed up to 512 MB. A larger ZIP file is refused with a message to unpack it and choose the folder instead. Importing needs the right to upload documents; without it you can see earlier imports but not start one. An import that stops partway shows as Interrupted.
Fidrel does not connect to your old system; the import reads a folder, a ZIP file or a CSV that you give it. Comments, markups, review history, statuses and access rules in the old system do not come with the files. An imported file arrives with the status Working and without a revision of its own; a revision read from its name is kept in the version’s details. An import never overwrites a document that is already there; it skips it, or adds the file as a new version.
Your trial applies to your first own project and starts when that project is created. No card required. Afterwards, choose card or invoice to continue.

The project system of the future connects people, documents and decisions. Discover the thinking behind Fidrel.
Read more
On site, answers need to be close at hand. Fidrel displays DWG drawings in your mobile browser, within the project’s document structure.
Read more
When everyone can see the next step, moving the project forward becomes easier. Fidrel brings activities, dates and reported progress together in a shared Gantt view.
Read moreMoving an archive
Anything else on your mind? We are happy to help.
Talk to usClean the file names, test with one folder, then use the Import center to bring in a folder or a ZIP file with the structure kept. Review every row before it is saved, and import larger archives in parts.
Yes. Drop a ZIP file or choose a folder, and the folders are kept and merged with existing folders of the same name. A CSV with one path per line creates only the folders, without files.
You choose. A document that already exists is skipped, or the file is added to it as a new version, and files that are unchanged are always skipped. Nothing is overwritten.
One import takes up to 5,000 files and 5 GB. A ZIP file can be up to 1 GB and each file up to 50 MB, with IFC models up to 512 MB. Split anything larger into several imports.
No. Only files and folders move. Imported files come in as Working, and comments, markups and review history stay in the old system. Set the statuses afterward, in groups if you like.