Set up your Maia account🔗

Before migrating your first workloads from Matillion ETL to Maia, ensure you have completed all the prerequisite steps discussed here.

Register for a Maia account🔗

If you don't have a Maia account, you must register for one.

Add users🔗

Any members of your organization who will be using Maia must be added as users. Read Manage other users for details.

Note

Your users can use Single Sign-On (SSO) to access Maia. Read Single sign-on setup for more information.

Logging into Maia with the User Admin role, you should see the Design data pipelines tile. If you don't see it, it may not yet have been enabled for the user. Follow the process given in Edit user roles to add Designer access for your users. If you follow that process and don't see the option to add Designer access, contact your Matillion Account Manager for further assistance.

Use Maia🔗

Once you have an account, it's immediately available for building new workloads. We recommend that you experiment with building pipelines to familiarize yourself with Maia before beginning any migration projects. It's perfectly safe to create projects and pipelines and perform as much testing and experimentation as you wish. Nothing you do at this stage will affect your subsequent migration of production workloads.

In particular, familiarize yourself with:

The new architecture
Designer
- New mechanisms for:
  - Git
  - Secrets and OAuths
  - Scheduling
- New features such as:
  - Lineage
  - AI

Note

Contact your Matillion Account Manager to discuss potential billing changes when you begin using Maia to run pipelines.

Prepare Maia🔗

Before migrating your first job, you need to create certain elements within Maia: a project, an environment, Git branches, and credentials. Although all of these elements have analogs in Matillion ETL, they're not suitable for automatic migration, and so you must manually create them to prepare Maia to import and run your migrated workloads.

You should spend some time planning how you want your pipelines to be organized in Maia—the structure of projects and project folders, for example—before you begin any migrations.

Projects🔗

Create a project where you want to import your migrated pipelines to, as described in Projects. Later you can add additional projects if you want to segregate your pipelines.

Environments🔗

Create an environment, as described in Environments.

Branches🔗

Your project will have a main branch created by default, but good practice is to perform all development work in a different branch, and only merge the work into main when ready for production. Therefore, we recommend you create a new branch with some appropriate name, such as metl-migrations, to hold the migrated pipeleines. Read Branches for details.

Credentials🔗

For security reasons, we do not migrate credentials such as secrets, passwords, or OAuths from Matillion ETL to Maia. Any secrets or other credentials you have set up in Matillion ETL will have to be recreated manually in Maia to allow your pipelines to run. Read Secrets and secret definitions, Cloud provider credentials, and OAuth for details.