When replacing Meridian with Greendocs makes sense
Accruent describes Meridian Enterprise as an engineering information management and asset lifecycle information management system, with solutions for industries such as chemicals, pharmaceuticals, oil and gas, metals and mining, and utilities. Many companies in Brazil and Latin America have years of records in a Meridian vault. When the decision is to move off it, Greendocs is one option: W3K describes it as an integrated GED, BPMS and EDMS platform, web-based, with ECM, BPM and low-code engines, configurable workflows, OCR search, CAD viewing and historical records. GED is the Brazilian term for document management.
29docs is a W3K Value Added partner and also a vendor-agnostic engineering document management consultancy. That is why the assessment compares paths before recommending the switch. If the target is still open, see also Meridian to ProjectWise migration and independent consulting for platform selection.
Questions that help you decide
Before choosing Greendocs as the target, answer these honestly:
- Who needs access to the archive? If contractors, construction sites and field teams need to view and approve documents in a browser, a web platform counts in its favor.
- Is the problem only document control, or process too? Greendocs combines document management with workflow automation. If what slows operations down is approval by email and parallel spreadsheets, that matters.
- How much work depends on CAD integration? Teams who work all day with references between drawings should test that use in the pilot, with their own files.
- What customizations does Meridian have today? Scripts, calculated properties and integrations need a destination, or a conscious decision to drop them.
The answers feed the assessment and decide whether the migration goes ahead, and in what order.
What moves from Meridian to Greendocs
According to Accruent’s documentation, a Meridian vault has two parts: a database with properties, navigation views, document types and workflow definitions; and content files with every revision, thumbnail, rendition and redline. Each element needs a home in Greendocs.
| In Meridian | In Greendocs | What needs a decision |
|---|---|---|
| Vault and navigation views | Folder structure, classification and search | Which organization becomes structure and which becomes a search filter |
| Document types and properties | Configured document types and fields | Property → field matrix, with value lists and required fields |
| Revisions | Document revision history | All or only issued ones; engineering revision in its own field |
| Document type workflow or workflow definitions | Configurable BPM workflows | Redesign the approval flow and map each document’s current state |
| CAD and custom references | Relationships between documents, per configuration | How to represent master → reference and check it in the report |
| PDF or DWF renditions and redlines | Files linked to the document | Move existing ones or regenerate |
| Audit log | Greendocs historical records and logs | The old log is kept as a searchable record, not replayed |
| Security and roles | Greendocs access controls | Redesign profiles in the target’s model |
Properties and document types
Meridian document types often carry dozens of properties, some from lookup lists, others calculated by scripts. In the migration, each becomes a Greendocs field, a fill rule, or is dropped with a documented reason. It is the moment to settle your engineering document numbering standard, without losing the original number.
Workflows and states
In Meridian, workflows are made of states and transitions, and the state name becomes the document’s status. Workflow definitions allow parallel routing and transitions that create revisions. In Greendocs, the process is redesigned as a configurable workflow. Two things must be right: the design of the new workflow and each migrated document’s position in it, so an approved document does not fall back to “in progress”.
References between documents
Meridian references link documents to each other: AutoCAD xrefs, MicroStation model references, assemblies and custom types. How those relationships are represented in Greendocs is settled in the configuration, with W3K, and the reconciliation report checks each migrated relationship.
Audit history
Meridian logs vault actions in an audit log that may live in its own database: creation, deletion, state changes, logons and configuration changes. That history does not become a native Greendocs record, since Greendocs logs what happens in Greendocs. The practice is to extract the log, keep it as a searchable record and link it to the migrated archive.
How 29docs runs a Meridian to Greendocs migration
The project follows the stages of the 29docs method, namely assessment, organize, standardize and make available, and a staged migration pipeline, repeated batch by batch:
- Extract metadata and files from the Meridian vault. Accruent documents archiving documents and metadata out of a vault, with a choice of formats and revisions, for import into another system.
- Transform and normalize: apply the mapping matrix and standardize codes, revisions, dates and states.
- Validate each document against quality rules agreed with you. Only a batch that meets the agreed thresholds moves on to loading.
- Load into Greendocs: documents, revisions, fields, workflow position and relationships.
- Validation and reconciliation reports comparing Meridian and Greendocs, document by document.
The pilot batch should include the hard cases on purpose: a master drawing with xrefs, a document with a long revision history, a superseded document and a document halfway through approval. Key users from engineering and document control check the pilot in Greendocs before the first production wave.
Greendocs configuration runs alongside the migration. If you do not have Greendocs yet, Greendocs implementation and the migration become a single project. See how Greendocs is used in fertilizer plants and how the 29docs and W3K partnership works.
29docs’ Meridian experience comes from projects such as the Petrobras case, where the engineering records of three fertilizer plants were organized, standardized and made available in a single, fully validated Meridian environment.
Cut-over and rollback
- Waves: the archive loads by project, site or discipline, lowest risk first.
- Freeze: the date Meridian goes read-only.
- Final delta: load of everything changed since the last wave.
- Acceptance: criteria that release Greendocs as the system of record.
- Rollback: triggers, owners and the path back to Meridian.
Meridian is switched off only after formal acceptance.
Risks of migrating from Meridian to Greendocs
- non-standard source metadata that blocks validation;
- engineering revision confused with system revision;
- a new workflow designed without the people who approve documents every day;
- CAD references left unchecked after loading;
- Meridian customizations, such as calculated properties and events, forgotten in the mapping;
- Meridian and Greendocs both live for lack of acceptance criteria.
What you get
- an inventory of the Meridian vault;
- an approved Meridian → Greendocs mapping matrix;
- workflow designs for Greendocs;
- validation rules and quality thresholds per batch;
- validation and source × target reconciliation reports;
- a cut-over and rollback plan;
- post go-live support on a block-of-hours basis.
How it starts
With a free 30-minute assessment. We look at the source vault, your approval processes, approximate volume and timing constraints. If it makes sense to continue, the next step is a vault inventory, which grounds scope, schedule and proposal.
Updated on .