Skip to content

Meridian to Greendocs migration

A Meridian to Greendocs migration moves an engineering archive from an Accruent Meridian vault into Greendocs, W3K's web platform for document and process management. 29docs, a W3K Value Added partner, maps Meridian properties, revisions, workflow states and references to the Greendocs configuration and proves every batch with validation and reconciliation reports.

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 MeridianIn GreendocsWhat needs a decision
Vault and navigation viewsFolder structure, classification and searchWhich organization becomes structure and which becomes a search filter
Document types and propertiesConfigured document types and fieldsProperty → field matrix, with value lists and required fields
RevisionsDocument revision historyAll or only issued ones; engineering revision in its own field
Document type workflow or workflow definitionsConfigurable BPM workflowsRedesign the approval flow and map each document’s current state
CAD and custom referencesRelationships between documents, per configurationHow to represent master → reference and check it in the report
PDF or DWF renditions and redlinesFiles linked to the documentMove existing ones or regenerate
Audit logGreendocs historical records and logsThe old log is kept as a searchable record, not replayed
Security and rolesGreendocs access controlsRedesign 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:

  1. 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.
  2. Transform and normalize: apply the mapping matrix and standardize codes, revisions, dates and states.
  3. Validate each document against quality rules agreed with you. Only a batch that meets the agreed thresholds moves on to loading.
  4. Load into Greendocs: documents, revisions, fields, workflow position and relationships.
  5. 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 .

Frequently asked questions

Why replace Meridian with Greendocs?

Every case has its own reasons, and 29docs does not start from the switch as a given. Common ones are web access for teams and contractors, process automation beyond document control and a preference for a Latin American vendor. W3K describes Greendocs as combining ECM, BPM and low-code engines. The assessment confirms whether the switch makes sense for your archive.

Do operations stop during the migration?

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

How long does a Meridian to Greendocs migration take?

It depends on the number of documents and revisions, document types and properties, workflows to rebuild, CAD references and metadata quality. 29docs commits to a schedule only after the vault inventory and a pilot batch.

Who keeps the data?

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

Are Meridian workflows recreated in Greendocs?

They are redesigned, not copied. Meridian works with states and transitions; Greendocs offers configurable workflows. A migration is a good moment to review the approval process: states nobody uses go away, and steps that now rely on email can become part of the workflow.

How do you prove nothing was lost?

With checks before and after loading. Before, each document is tested against quality rules, and only batches that meet the agreed thresholds move on. After, a report compares source and target document by document: counts, properties, revisions, states and references.

Is there a rollback plan?

Yes. Meridian stays read-only until Greendocs is formally accepted, and the plan sets stop triggers, decision owners and the path back in advance. Loads run in traceable batches, so a faulty batch can be removed and reloaded.

What drives the cost of a Meridian to Greendocs migration?

Data volume and quality, the number of document types and properties, revisions to keep, workflows to redesign, CAD references, renditions and redlines, audit requirements and the cut-over window. Greendocs licensing is a separate item from the migration service.

Can we migrate only part of the archive?

Yes. It is common to migrate one project, one site or the current archive first, and keep older history in a searchable archive. The wave plan is set from the vault inventory.

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.