Skip to content

EDMS migration for engineering archives

An EDMS migration moves an engineering archive from one platform to another while keeping each document's context: metadata, revisions, approval state, references between files and history. 29docs migrates between platforms such as Meridian, ProjectWise and Greendocs with a pipeline that validates every batch before loading and proves the result with reconciliation reports.

Why EDMS migration is an engineering project, not an IT task

EDMS migration is often treated as a file transfer. That is an expensive mistake. An engineering document is worth its context: number, discipline, area, issued revision, approval state, who approved it, which drawings it references and which reference it. Lose the context and the target system receives files, not a controlled archive.

Accruent’s documentation shows the scale of the problem. A Meridian vault keeps metadata, navigation views, document types and workflow definitions in its database, and every revision, thumbnail, rendition and redline in its content files. Each target platform organizes that differently, so migrating means translating between data models.

29docs is a Brazil-based, vendor-agnostic engineering document management consultancy that does not sell licenses. That leaves us free to design the migration around your archive, not around a product.

System-to-system migration, not scanning

Searches for “document migration” often mix two different jobs. One is scanning: turning paper into files and indexing them. The other is moving an archive that is already digital from one document management platform to another, be it an EDMS, an ECM or what Brazilian companies call a GED. This service covers the second.

The difference changes the whole project. In scanning, the challenge is capture and indexing. In a system-to-system migration, the metadata already exists but follows the old platform’s rules, and the risk is losing or distorting it in transit. A scanned drawing has a number and a file. The same drawing in an EDMS has dozens of properties, several revisions, an approval state, xrefs and a record of who did what. Moving all of that takes field-by-field mapping and an objective way to prove the target matches the source.

When does a company need to migrate its EDMS?

The usual triggers:

  • platform change after a corporate decision, alignment with a global parent or the end of a contract;
  • consolidation of several systems or vaults after an acquisition or reorganization;
  • change of model, such as moving from an on-premises server to a web or SaaS platform;
  • retiring unsupported legacy systems whose archive must stay accessible for operations and audits;
  • project handover, when an EPC contractor’s documentation moves into the asset owner’s system.

If the open question is which platform to choose, independent consulting comes before the migration.

What moves and what needs a decision

ElementMoves as is?What to decide
Native files: DWG, DGN, Office, PDFYesObsolete formats and corrupt files: convert, archive or discard
MetadataWith mappingField by field: target, data type, value lists, required fields
RevisionsWith mappingAll or only issued ones; separate engineering revision from system version
Workflow statesWith mappingState-by-state map; documents must land in the right target state
References between files, or xrefsUsually not on their ownRebuild relationships in the target and check them in the report
Renditions and redlinesDepends on the platformMove existing ones or regenerate; keep those of issued documents
Audit historyRarely in native formExtract and keep as a searchable record
PermissionsShould notRedesign groups and access in the target’s model

Two examples from official documentation show why references and states need attention. Bentley explains that when documents are imported into ProjectWise, physical relationships between files are kept but are not recognized by the system until references are scanned. And when a workflow is assigned to a ProjectWise folder, documents are placed in its first state. Untreated, an approved drawing arrives as a draft.

How 29docs runs an EDMS migration

The method starts with an assessment and moves through three steps: organize, standardize, make available. In execution, we use a staged pipeline, repeated batch by batch:

  1. Extract metadata and files from the source, using the tools and interfaces the platform provides. Accruent, for example, documents exporting documents and metadata out of a vault with its archive wizard, for import into another system.
  2. Transform and normalize: apply the mapping matrix and standardize codes, dates, revisions and states.
  3. Validate each document against quality rules agreed with you. Only a batch that meets the agreed quality thresholds moves on to loading. The rest goes back with its reason.
  4. Load into the target, scripted and repeatable, creating documents, revisions, metadata, states and relationships.
  5. Validation and reconciliation reports comparing source and target, document by document.

The pipeline runs on a pilot batch, then in waves, then on the cut-over delta. Every run leaves a trail: what went in, what was left out and why.

The pilot matters more than it looks. It should include the awkward cases on purpose: a drawing with many xrefs, a document with a long revision history, a superseded document, a file in an old format and a restricted record. If the pilot only carries easy documents, the problems show up in production, when they cost more.

With the archive migrated and in order, AI for engineering documents can answer technical questions about it.

Migrations 29docs handles

  • Meridian to ProjectWise migration: from an Accruent vault to a Bentley datasource.
  • Meridian to Greendocs migration: from Meridian to W3K’s web platform. 29docs is a W3K Value Added partner.
  • Migrations and consolidations involving Hexagon SDx, Oracle Aconex, Siemens Teamcenter, Siemens COMOS, AVEVA AIM, Construtivo and E-clic, assessed case by case.

29docs has also organized whole archives within a single platform, as in the Petrobras case: the engineering records of three fertilizer plants standardized in one fully validated Accruent Meridian environment.

Planning, cut-over and rollback

The cut-over plan answers five questions before the first production batch:

  • in which waves the archive will load, and in what order;
  • when the source goes read-only;
  • how the final delta will be captured and loaded;
  • which acceptance criteria release the target as the system of record;
  • who can stop cut-over, on which triggers, and how to fall back to the source.

The source is switched off only after formal acceptance. Until then it stays read-only as a reference.

Common risks in engineering document migration

  • Dirty metadata: non-standard codes, empty fields and duplicates. They surface in validation, which is where you want them.
  • Revision confused with version: the engineering revision, such as Rev 0 or Rev A, needs its own field.
  • Broken references: master drawings without managed xrefs in the target.
  • Wrong states: approved documents arriving as drafts.
  • Customizations with no equivalent: rules and scripts in the source that must be redesigned.
  • Two live systems: a cut-over without acceptance criteria, with teams working in both.

What you get

  • an inventory of the source archive;
  • an approved mapping matrix;
  • validation rules and quality thresholds per batch;
  • validation and source × target reconciliation reports;
  • a cut-over and rollback plan;
  • documented scripts and procedures, which stay with you;
  • post go-live support if you want it, on a block-of-hours basis.

How it starts

With a free 30-minute assessment. We talk about source, target, approximate volume, business deadlines and audit requirements. If it makes sense to continue, the next step is an inventory of the source, which grounds scope and schedule. 29docs serves capital-intensive industries such as mining, oil and gas and energy across Brazil and Latin America.

Updated on .

Frequently asked questions

How is an EDMS migration different from document scanning?

Scanning turns paper into digital files. An EDMS migration moves documents that already live in one electronic system into another, together with metadata, revisions, workflows and references. 29docs works on system-to-system migration, in the context of engineering document management.

Do operations stop during an EDMS migration?

Not for most of the project. Extraction, transformation, validation and test loads run while the source system stays in use. Downtime is limited to cut-over, when the source goes read-only and the final delta is loaded. The window is measured in rehearsals and written into the plan.

How long does an EDMS migration take?

It depends on the number of documents and revisions, document types and fields, workflow complexity, references between files and the quality of the source metadata. 29docs commits to a schedule only after the source inventory and a pilot batch, which show the real extraction and load rates.

Who owns the data during the migration?

You do. The work runs in your environment or one you approve. At the end, 29docs hands over the mapping matrix, validation rules, reports and documented scripts, and keeps no copy of the archive.

How do we know the migration is right?

Through reports, not visual spot checks. Before loading, each document is tested against quality rules, and only batches that meet the agreed thresholds move on. After loading, a report compares source and target document by document: counts, metadata, revisions, states and references.

What if something goes wrong at cut-over?

The source system is not switched off at cut-over. It stays read-only until the target is formally accepted, and the rollback plan sets triggers, owners and the path back. Because loads run in traceable batches, a faulty batch can be removed and reloaded.

What drives the cost of an EDMS migration?

Volume, source metadata quality, the number of document types and fields to map, how many revisions to keep, custom workflows, CAD references, regulatory validation requirements and the available cut-over window. 29docs does not publish prices because these factors vary widely from one archive to the next.

Which platforms do you migrate between?

29docs works with Accruent Meridian, Bentley ProjectWise, Hexagon SDx, Oracle Aconex, Siemens Teamcenter, Siemens COMOS, AVEVA AIM, W3K Greendocs, Construtivo and E-clic. For other sources, the assessment checks whether metadata and files can be extracted reliably.

Should we change our document numbering during the migration?

Sometimes, but it adds risk. New codes break external references such as vendor document lists and maintenance systems. The safer route is to keep the original code in an attribute and introduce the new one alongside it. Our engineering document numbering guide helps with that decision.

Ready for your next audit?

A 30-minute conversation. No pitch. We want to understand your document reality before talking about any solution.

We reply within 1 business day. Your data is never shared.