WordPress database error: [Table 'wp_stemmadocs.wp_eazydocs_view_log' doesn't exist]
SELECT count FROM wp_eazydocs_view_log WHERE post_id = '5606' AND created_at = '2023-05-30' /* From [] in [/nas/content/live/stemmadocs/wp-content/plugins/eazydocs/includes/Frontend/post-views.php:42] */

WordPress database error: [Table 'wp_stemmadocs.wp_eazydocs_view_log' doesn't exist]
SHOW FULL COLUMNS FROM `wp_eazydocs_view_log` /* From [] in [/nas/content/live/stemmadocs/wp-content/plugins/eazydocs/includes/Frontend/post-views.php:47] */

Migrate from existing Amundsen

Estimated reading: 2 minutes

Migrating from Amundsen involves three main steps:

  1. Migrating existing metadata from Amundsen to Stemma
  2. Ingesting metadata continuously
  3. Cut over

1 – Migrating existing metadata from Amundsen to Stemma

In this step, you take all the existing metadata from Amundsen and load it into Stemma. The metadata imported includes, but is not limited to:

  • Table and column descriptions
  • Tags
  • Ownership information

To import this metadata, upload a dump of your Amundsen neo4j metadata into Stemma:

  1. Bring the Amundsen storage offline.
  2. Use dump -> load, available on all neo4j installations, to dump and upload your data.

After import, your Stemma instance will be up to date with your Amundsen instance. However, Stemma has a significant number of additional features so the layout will appear different. Check out the quick start page here:

Multi-step column-level lineage on the Lineage tab of table details in Stemma

But your data won’t be periodically updated until you enable periodic updates; see the next step.

2 – Ingesting metadata continuously

You need to configure Stemma to ingest metadata updates on an ongoing basis. Once this configuration is done, you won’t need Python databuilder jobs to ingest data.

Information ingested in this step includes:

  • Table and column names
  • Linked issues (JIRA tickets)
  • Frequent users
  • Lineage, if it exists

IIn Stemma’s Admin interface, provide credentials to your data sources to allow Stemma access to extract metadata on an ongoing basis:


Stemma will now do the work to “upsert” metadata updates, as they occur, into the data you uploaded from Amundsen in the previous step.

3 – Cut Over

At this point, Amundsen and Stemma are running side-by-side, and Stemma recommends sharing access to Stemma with your power users and getting their feedback to ensure all of their use-cases are supported. Usually one week of overlap to obtain feedback and an additional week to incorporate feedback, if applicable, is sufficient.

When all looks good, simply redirect the URL of your internal Amundsen to the Stemma URL.

If you have any feedback or questions about moving from Amundsen to Stemma integration, please reach out to s[email protected]!