# How to map Apple School Manager users to Hexnode users in bulk?

Overview
--------

When integrating Apple School Manager (ASM), users and classes are automatically synced to the Hexnode portal. If these users already exist in Hexnode (as Local or Directory users), a duplicate profile is created. To resolve this and consolidate data, administrators can perform a Bulk Map to merge ASM identities with existing Hexnode profiles.

**Administrative Navigation**

All mapping actions are performed within the **Manage** tab of the Hexnode UEM console.

Step-by-Step: Bulk Mapping Workflow 
------------------------------------

1. Navigate **to Manage** > **Users**.
2. Click the **Map users in bulk** button.
3. **Data Preparation**: 
    - Download the Sample CSV file provided in the pop-up.
    - Input the user details, ensuring the format matches the sample exactly to prevent processing errors.
4. **Upload & Execute**: 
    - Upload your completed CSV file.
    - Click **OK** to initiate the mapping process.

Frequently Asked Questions (FAQs) 
----------------------------------

1. **Why do I see two different profiles for the same student/teacher after ASM integration?** This happens because the ASM sync creates new “Managed Apple ID” profiles. If the user was already manually added to Hexnode as a Local user, the system treats them as two separate entities until they are manually mapped.
2. **What is the result of a successful “Mapping” action?** Once mapped, the existing Hexnode user profile is merged with the Managed Apple ID. The two profiles are consolidated into a single ASM/Local user entity, retaining the attributes of both.
3. **Is it possible to map users individually instead of in bulk?** Yes. While this guide covers the bulk CSV method for large deployments, individual mapping can be performed directly within a specific user’s profile settings in the Manage tab.
4. **Why is it recommended to use the sample CSV file?** Database parsers require strict header alignment. Using the sample file ensures that fields like “Managed Apple ID” and “Hexnode Username” are mapped to the correct database columns, reducing sync discrepancies.