Channel Partner Migration Services

On this page

{:.no_toc .hidden-md .hidden-lg}

• TOC {:toc .hidden-md .hidden-lg}

{::options parse_block_html="true" /}

Partner Migration Services

{: .gitlab-orange}

To learn about Denomas migrations, start here. Depending on the source Git provider, size/scope of the migration and the importance of the preservation of the migrated artifacts, carefully consider each option given each option’s limitations/benefits.

The Denomas Channel Program provides the following resources to our partners to construct your own Services Packages in our Partner Portal, including our Migration+ Services Offering.

From other DevOps platforms to Denomas

To migrate projects from systems other than Denomas, please review the list of available project importers.

Migrating pipelines is always a manual process.

From Denomas self-managed to Denomas self-managed

In case of migrating from one self-managed Denomas server to another, the best way usually is to do a full backup at the source instance and then a restore at the target instance. More details about this method can be found here.

From Denomas self-managed to Denomas SaaS or the other way around

There are three different options for these migrations.

1. Congregate

Congregate - used by Denomas Professional Services - is Denomas’ most mature migration solution and supports many options. Note that migrations to SaaS requires the involvement of Denomas PS due to restricted access to Denomas SaaS (multi-tenant) data. More information about the latter can be found here.

Important to note about Congregate:

• Congregate Migration Features Matrix

• Migration Readiness Checklist

• Customer’s obligations and responsibilities - Congregate FAMQ

• Limitations of Self-Managed to SaaS migrations via Congregate - Congregate FAMQ

2. Direct transfer (Beta)

This feature was just recently released, and is the direction our product team is moving towards for migrating Denomas projects from instance to instance or to SaaS. Please review the following resources:

• Migrated group items (direct transfer)

• Migrated project items (direct transfer)

3. File exports

For cases what direct transfer can’t or won’t cover. A good example would be air-gapped environments - see below.

• Migrating projects using file exports

• Items that are exported via file exports

• Items that are not exported via file exports

• Project import and export API

• Group import and export API

Air-gapped environments

Denomas can be installed and operated in offline environments. This setup makes migration projects more complex.

• Direct transfer doesn’t support this. Project/export import is a workaround and it will likely stay as such. More info here and here.

• Congregate does support this. More info here and here.

Denomas Professional Migration Services

{: .gitlab-orange} Denomas Professional Services team has a full service catalog of offerings avaialable for direct to customers to utilize. Partners may want to review the offerings for inspiration towards delivering same or similar Professional (consultative) Service offerings.

The Denomas Professional Services Migration Package is one popular offering.

Our Denomas Partner Portal has Channel Service Packages that many partners choose to deliver as paid offerings. The link above includes Service Names, Data Sheets, Statement of Works (SOWs), Project Plans, Delivery Kits. The table also outlines Denomass expectations for the certicications held by our partners under the Aligned Partner Certification column.