> For the complete documentation index, see [llms.txt](https://motivlabs.gitbook.io/impulse-user-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://motivlabs.gitbook.io/impulse-user-manual/cookbook-recipes/content-aligner.md).

# Aligning Content between Endpoints

### Case 1: Content between endpoints already exist but have different ids

Assume there are 6 contents of type `Bed` in the source endpoint and 6 contents of type `Bunk` in the destination endpoint. You want to be able to sync those contents without creating duplicates. They have manually been created and have different ids. They have a `code` field that is unique across each endpoint and can be used to align the contents because they match across endpoints.

![](/files/uPS6y3W0VRaH0whBk6IZ)

#### Solution

ImpulseSync can solve this by using the [Content Aligner](/impulse-user-manual/getting-started/content-mapper/aligner-fields.md) in the content mapper.

**Step 1: Create a job to sync the content type: `Bed` -> `Bunk`**

* First we create the job to sync the content type: `Bed` from the source endpoint to `Bunk` into the destination endpoint.

![](/files/fIOwTCGRnJRHFwNhjlaL)

**Step 2: Set up the content mapper**

* Next we set up the content mapper. Go to `Field Aligning` section and set the `Source Aligner Fields` property to `code` (the id of the field in the source endpoint) and the `Destination Aligner Fields` property to `code` (the id of the field in the destination endpoint).

![](/files/twbjcCVPQnrdxbFlvarY)

**Step 3: Run the job**

* Now we can run the job and see the results.