---
sidebar_label: Sync services
doc_id: 8c5fd501-3cb1-4eba-8347-3246dd4a4fe3
description: >-
  Sync service configurations across environments to promote changes from
  development to staging/production easily.
keywords:
  - service synchronization
  - environment promotion
  - configuration management
  - deployment
  - DevOps
title: Sync one service with another
canonical: 'https://docs.nullplatform.com/docs/services/sync-service'
---
# Sync one service with another

You can **sync a service with an existing one** by comparing their configurations. This makes it **easier and faster to
promote services** across environments, with fewer chances of mistakes.

:::info 
This feature **does not support** imported services, such as monitoring tools (e.g., New Relic), AI services
(e.g., OpenAI), or other third-party integrations.
:::

## How it works

1. Head to your application’s **Development** dashboard and open the **Services** view.
2. Find the service you want to sync up and click **Manage > Sync service with another**.
3. Select the service to sync from and which settings to apply.
4. Make any changes you need, like updating the target dimensions or environment.
5. Click **Create service** to finish.

## Use case

For example, you might update a service in development and want to promote those changes to staging. 
You’ll select the staging service you want to sync and the source service to sync from.

You can compare attributes and review new, removed, and modified values, then choose which attributes to sync.

You can also review attributes that are ignored in this flow because they can’t be copied, like identifiers.

Once you define the settings, review and confirm the changes.

## Common use cases

Syncing a service with an existing one can help your development and operations workflow, not
just when you’re setting things up for the first time.

Here are some common scenarios where this feature is useful:

- **Promoting services across environments.** Let’s say you’ve finished configuring a service in your *Development*
  environment. You can use that same setup to sync services in *Staging*, and then do the same for
  *Production*, saving time and reducing manual work.

- **Iterating over time.** Once services exist in all your environments, you’ll likely need to revisit and improve them. You can **synchronize changes** across environments instead of creating new services
   each time. 
By reducing the amount of data you need to input manually and preloading as much as possible, this feature helps teams
avoid mistakes and move faster.