# Manage Integrations

### Reassign an account to a different entity

You can change the entity associated with a connected account without disconnecting:

1. Go to the **Accounts** tab
2. Click the options menu (⋯) on the account row
3. Click **Settings**
4. Change the entity in the **Details** section

***

### Change the start or end date

The connection start date controls when transaction data begins syncing. It defaults to the entity's bookkeeping start date. The end date controls when syncing stops — transactions after the end date will not appear in Kick.

To change either date:

1. Go to the **Accounts** tab
2. Click the options menu (⋯) on the account row
3. Click **Settings**
4. Click **Edit** next to the **Start date** or **End date**
5. Pick a new date and click **Set Date**

To remove a date override and revert to the entity default, click **Clear date** in the date picker.<br>

{% hint style="warning" %}
**Important:** Changing the start date can pull in additional historical transactions or remove transactions outside the new range. Adjust with care if categorization or reconciliation work has already been done.
{% endhint %}

***

### Fix a disconnected account

Bank and financial account connections can occasionally disconnect due to credential changes, multi-factor authentication updates, or connectivity issues with the institution. When this happens, the affected account will display a connection error on the Accounts tab.

#### Reconnect an account

1. Go to the **Accounts** tab
2. Click **Fix connection** on the affected account
3. Re-authenticate with your bank or financial institution

Once reconnected, Kick automatically syncs any missed transactions.

#### Credential changes (new account number or login)

If your bank issued new credentials or a new account number (e.g., due to fraud, a card replacement, or an account migration), the **Fix connection** flow may not resolve the issue — the bank treats it as a new account through Plaid.

To maintain continuity:

1. On the **Accounts** tab, click **Add Account** and authenticate with the new credentials.
2. Once the new account is connected, merge it with the original account to consolidate transaction history and avoid duplicates.

#### Re-enable a disabled account

If an account was disabled rather than fully removed, it will appear grayed out on the Accounts tab. Toggle the **Connected to Plaid** switch back on — no need to go through Plaid again.

#### Re-add a deleted account

If you previously deleted a bank account and want to add it back:

1. On the **Accounts** tab, click **Add Account**
2. Search for your bank and authenticate through Plaid
3. Select the specific account(s) you want to reconnect

***

### Merge accounts

When an account is reconnected with new credentials — or when you need to consolidate two accounts that represent the same underlying bank account — use Merge Accounts to combine them without losing transaction history or creating duplicates.

#### Where to find it

Go to **Settings → Accounts**, then open the **Account details** panel for the account you want to merge. If the account is eligible, you'll see a **Merge account** button.

{% hint style="info" %}
**Note:** The merge option is not available if the account has locked transactions.
{% endhint %}

#### Select accounts to merge

1. Click **Merge account** to open the merge modal.
2. The **Merge** field is pre-filled with the account you started from — this is the account that will be absorbed and removed.
3. In the **into** field, search for and select the destination account. Only accounts on the same entity are available.
4. Use the **Flip accounts** button to swap the source and destination if needed.

The modal will confirm: "This will move all transactions from \[source account] into \[destination account] and remove \[source account]."

Click **Preview merge** to continue. This does not modify any data.

#### Preview the merge

The preview runs a dry-run analysis comparing both accounts and shows what will happen:

**Transactions to be moved** — Transactions that only exist on the source account will be relocated to the destination.

**Deduplicated transactions** — If both accounts contain transactions with the same amount on the same date, they will be flagged as duplicates. Expand this section to review them. The system keeps one copy and removes the other.

**Conflicts** — Two types of conflicts may require your input:

* **Both modified** — A duplicate transaction was found in both accounts, but each copy has been manually edited (e.g., different categories or memos). Select which version to keep.
* **Multiple matching** — A transaction in the destination matches more than one transaction in the source (e.g., two identical charges on the same date). Select the correct pairing.

The **Merge** button is disabled until all conflicts are resolved.

#### Execute the merge

Once all conflicts are resolved, click **Merge**. The system will:

* Move all non-duplicate transactions from the source to the destination
* Deduplicate overlapping transactions
* Regenerate journal entries for moved transactions
* Reassign bank and integration connections (Plaid, Stripe, etc.) from the source to the destination
* Remove the source account

If an additional conflict is detected during the merge, a prompt will appear asking you to resolve it before continuing. You can choose **Continue** or **Abort merge**.

#### After the merge

If the destination account now has multiple bank or integration connections, a **Merged accounts** section will appear in the account details. Each connection is listed with an **Extract** button, which lets you split that connection back out into a standalone account if needed.

#### Key details

* Accounts must belong to the same entity to be merged.
* Accounts with locked transactions cannot be merged.
* If the source account has manual journal entries on its ledger, you may need to address those before merging.
* There are no restrictions on mixing account types — you can merge based on entity ownership regardless of whether the accounts are bank accounts, credit cards, or other types.

***

### Pause a connection

To temporarily stop a connected account from syncing without removing it:

1. Go to the **Accounts** tab
2. Find the account and click the options menu (⋯)
3. Toggle off the connection using the switch next to the sync status

This stops future syncing but keeps all existing data intact. Toggle it back on at any time to resume.

***

### Remove a connected account

If you need to permanently remove an account from Kick:

1. Go to the **Accounts** tab
2. Find the account and click the options menu (⋯)
3. Click **Settings**
4. Scroll down and select **Remove account**
5. Choose one of the following:
   * **Remove all historical data and account** — permanently deletes the account and all associated transaction history
   * **Keep historical data and disable the account** — stops future syncing while preserving all existing transactions

{% hint style="info" %}
**Tip:** We recommend pausing the connection rather than removing it unless you're sure the data is no longer needed.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kick.co/setting-up/integrations/manage-integrations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.