Why a Meridian to ProjectWise migration is not a file copy
An engineering document in a Meridian vault is much more than a DWG or a PDF. Accruent’s documentation describes a vault in two parts. The first is a database holding the metadata, which Meridian calls properties, along with templates and the vault configuration, such as navigation views, document types and workflow definitions. The second is a folder structure of content files holding every revision, thumbnail, rendition and redline of each document.
ProjectWise organizes the same information differently. Attributes come from environments applied to folders, the lifecycle follows workflows and states, history lives in versions, and CAD references become logical sets. Migrating means translating one model into the other, document by document, and proving the translation is right.
That is what 29docs does. We are a vendor-agnostic engineering document management consultancy based in Brazil, working with Accruent Meridian and Bentley ProjectWise without selling licenses for either. If the target platform is still open, see also Meridian to Greendocs migration or the broader EDMS migration service.
What moves from Meridian to ProjectWise, and how
The table lists the parts of a Meridian vault, their ProjectWise counterpart and the decision each one needs. Descriptions follow Accruent’s and Bentley’s official documentation, listed in the sources at the end of the page.
| In Meridian | In ProjectWise | What needs a decision |
|---|---|---|
| Vault: database and content files | Datasource, with folders and work areas | One datasource or several; folder structure by project, site or discipline |
| Navigation views | Folder and work area structure | Which view becomes the physical folder tree; the rest become saved searches or attributes |
| Document types and properties | Environments, attributes and interfaces | Property → attribute matrix, with data types, value lists and required fields |
| Revisions, with vault history enabled | Versions: read-only snapshots, with one active version | Move every revision or only issued ones; how the engineering revision becomes an attribute |
| Document type workflow or workflow definitions, with states and transitions | Workflows and states assigned to folders | State-by-state map; documents must land in the right state, not the first one |
| CAD references: AutoCAD xrefs and MicroStation references | Logical sets | Rebuild master → reference relationships after the load |
| Custom non-CAD references | No direct equivalent | Keep as an attribute, a set or an entry in the report |
| PDF or DWF renditions and redlines | Document files or renditions generated in the target | Move existing renditions or regenerate them |
| Audit log | ProjectWise audit trail | The old log does not become a native trail; it needs its own retention |
| Security and roles | Folder and document access control | Redesign groups and permissions, do not copy one to one |
Properties, attributes and the mapping matrix
In ProjectWise, an environment is a set of organization-specific attributes created in ProjectWise Administrator and applied to folders and work areas. Each Meridian document type usually carries dozens of properties. Some are system fields, some come from lookup lists, some are calculated. The mapping matrix decides, for each one, which attribute receives the value, how it is transformed and what happens when it is empty or non-compliant. This is where your engineering document numbering standard has to be clear.
Revisions become versions
Meridian keeps every revision of a document when vault history is enabled. Bentley’s documentation defines a ProjectWise version as a read-only snapshot of a document at a point in time, with the original document becoming the active version. Two things need care. First, the system revision is not the engineering revision, such as Rev 0, Rev A or Rev 1, which needs its own attribute. Second, the load order must reproduce the historical sequence, from the oldest revision to the current one.
Workflow states
In Meridian, the name of a workflow state also becomes the document’s status value. In ProjectWise, when a workflow is assigned to a folder, documents in that folder are placed in the first state. Left untreated, an approved document would land in the target as “work in progress”. The load has to place each document in the state equivalent to its source state, following the agreed state map.
References and xrefs
Meridian references link one document to another: AutoCAD xrefs, MicroStation model references, assemblies and custom types defined by the administrator. Bentley notes that when documents are imported into ProjectWise, physical relationships between files are kept but are not yet recognized or managed by ProjectWise. Logical sets only exist after the reference scanning wizard runs, or after a load that creates the relationships explicitly. That step belongs in the plan and in the reconciliation report.
Renditions, redlines and audit history
Renditions are copies of a document in another format, usually PDF or DWF, produced by Meridian’s Publisher. ProjectWise offers automated PDF renditioning, so the question is whether to migrate old renditions or regenerate them. For issued documents, the approved rendition often has record value and should be kept. The Meridian audit log, which may sit in a separate database, does not become a native audit trail: ProjectWise records what happens in ProjectWise. The answer is to extract that log and keep it as a searchable record.
How 29docs runs the migration
The work follows the stages of the 29docs method: assessment, organize, standardize and make available. Delivery runs on a staged migration pipeline, repeated batch by batch.
- Extract. Read metadata and files from the Meridian vault: documents, revisions, properties, states, references and renditions. Before extraction, checked-out documents are released and deleted documents are purged. Accruent asks for both steps in its own extraction procedure for Meridian Cloud, and the principle holds for any target.
- Transform and normalize. Apply the mapping matrix: standardized codes, checked value lists, normalized dates and revisions, translated states.
- Validate. Test each document against quality rules agreed with you. Only a batch that meets the agreed quality thresholds moves on to loading. Anything left out goes back with its reason, for correction at source or exception handling.
- Load into ProjectWise. Create documents, versions, attributes and states in the target datasource. Bentley publishes the pwps_dab PowerShell module, with commands to import documents, create versions, update attributes, set workflow state and build logical sets, which makes every load scripted and repeatable.
- Validation and reconciliation reports. Compare source and target document by document: counts, attributes, revisions, states and references. Mismatches are listed with cause and resolution.
The same pipeline runs first on a pilot batch, then in waves and finally on the cut-over delta. 29docs’ Meridian experience includes organizing and standardizing the engineering records of three Petrobras fertilizer plants in a single, fully validated Meridian environment. For a technical look at the risks, read our Portuguese-language article Migração de Meridian para ProjectWise: o que ninguém te conta antes de começar.
Planning and cut-over
A migration without a planned cut-over ends with two live systems and no one sure which is official. The plan sets:
- load waves, by project, site or discipline, starting with the lowest risk;
- freeze, the moment Meridian goes read-only;
- final delta, the load of everything changed since the last wave;
- acceptance criteria that must be green before ProjectWise becomes the system of record;
- rollback: who can stop cut-over, on which triggers, and how to return to Meridian without losing work.
Meridian is switched off only after formal acceptance. Until then it stays read-only as a reference.
What are the risks of migrating from Meridian to ProjectWise?
The problems that delay this kind of project are well known:
- dirty source metadata: non-standard codes, empty required fields and duplicates that only show up in validation;
- engineering revision confused with system version, blurring which document is the issued one;
- documents in the wrong state because the target workflow placed them in the first state;
- xrefs without logical sets, leaving master drawings without managed references;
- Meridian customizations, such as event scripts and calculated properties, with no direct equivalent, which must be redesigned in ProjectWise;
- cut-over without acceptance criteria, leaving both systems alive for months.
Each risk has a control in the pipeline: a validation rule, a column in the mapping matrix or a line in the reconciliation report.
What you get
- an inventory of the Meridian vault: document types, properties, workflows, revision volume, references and renditions;
- a Meridian → ProjectWise mapping matrix, approved by you;
- a proposed target structure covering folders, environments, attributes and workflows, validated with your ProjectWise administrators;
- validation rules and quality thresholds per batch;
- validation and source × target reconciliation reports, per batch and consolidated;
- a cut-over and rollback plan;
- documented load scripts and procedures, which stay with you;
- post go-live support through EDMS upgrade and support on a block-of-hours basis.
How it starts
It starts with a free 30-minute assessment. We look at the source vault, the target ProjectWise, approximate volumes and window constraints. If it makes sense to continue, the next step is a vault inventory, which grounds scope and schedule. Companies such as CBMM, ArcelorMittal, Evonik and Petrobras trust 29docs.
Updated on .