> For the complete documentation index, see [llms.txt](https://docs.kpnthings.com/kpn-things/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpnthings.com/kpn-things/the-portal-explained/things-manager/connectivity/m2m-connectivity-configuration/m2m-bulk-by-csv-file-actions.md).

# M2M Bulk by CSV file actions

The M2M Bulk by CSV file actions feature enables you to perform modifications on large numbers of SIMs through a file upload. Instead of updating SIMs individually, you can upload a CSV file containing the required data and configuration, allowing changes to be processed efficiently and consistently at scale.

The bulk update process consists of four steps:

* **Upload** – Upload the CSV file containing the data for the desired modification.
* **Validation** – The system verifies the file structure, content, and data integrity before proceeding.
* **Configuration** – Select the type of modification you want to perform and provide any required settings.
* **Execution** – Once the file has been validated and configured, the bulk action is executed on the selected assets.

Different modification types may require a specific CSV template or file structure. Before starting a bulk action, ensure that your file complies with the required format. By using Bulk Actions, large-scale changes can be performed in a controlled, repeatable, and efficient manner while reducing the need for manual updates.

<figure><img src="https://1453626848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl6RrePMSAjRvOgcHjMBZ%2Fuploads%2F395rULTmZeBQeJwNGDPS%2FBulk%20by%20CSV%20file%20button.png?alt=media&amp;token=fad422ec-b0c7-4efc-b8c1-4f6c1188b8ab" alt=""><figcaption></figcaption></figure>

This feature supports several modification types, each designed for a specific M2M use case. When creating a bulk action, select the appropriate modification type and use the corresponding CSV template.

#### Pair SIM Card with Device

Use this action to pair one or more SIM cards with devices in bulk. The uploaded file must specify both the SIM card identifier and the target device identifier for each record.

Typical use cases:

* Initial device deployment
* Migrating SIM cards to new devices
* Mass onboarding of connectivity-enabled assets

#### Unpair Connectivity

Use this action to remove the association between a SIM and a device. This is typically required when devices are decommissioned, replaced, or reassigned.

Typical use cases:

* Device replacement
* Asset retirement
* Connectivity cleanup

#### Change Connection Status

Use this action to modify the operational status of one or more SIM cards. Depending on the platform configuration, this may include actions such as activating, suspending, or reactivating connections.

Typical use cases:

* Temporary service suspension
* Reactivating inactive connections
* Managing connectivity lifecycle states

#### Change Communication Plan

Use this action to assign a different communication plan to selected SIM cards. Communication plans determine how devices communicate within the network and which services are available.

Typical use cases:

* Migrating devices between communication plans
* Enabling additional connectivity features
* Standardizing communication settings across device groups

#### Change Rate Plan

Use this action to change the billing or service plan associated with one or more SIM cards. This allows you to optimize costs and service levels based on device usage patterns.

Typical use cases:

* Upgrading subscriptions
* Downgrading unused capacity

#### Download Activation Codes

Use this action to generate and download activation codes for multiple eSIM profiles in a single operation. These activation codes can be used to download and install eSIM profiles on compatible devices.&#x20;

<figure><img src="https://1453626848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl6RrePMSAjRvOgcHjMBZ%2Fuploads%2F0Zt1vHpVmZa354F3A7J2%2FDownload%20Activation%20codes.png?alt=media&amp;token=7853415f-75f5-4370-9352-b55e99030292" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kpnthings.com/kpn-things/the-portal-explained/things-manager/connectivity/m2m-connectivity-configuration/m2m-bulk-by-csv-file-actions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.