This article explains how to export a contact list from the MAAC platform, and how to use the data mapping fields to organize your data or prepare an import update.
# Export a Contact List
Path:
Contact Management > Contact > "More actions" in the top-right corner > Export Contacts
Export format:
The export file is in
.csvformatUp to 100,000 contacts can be exported per export (depending on your contract plan)
Export options
Click Export in the top-right corner of the contact page to choose the export scope:
- Export all contacts
- Export reachable contacts
- Export not reachable contacts
- Export conflict contacts — download the list of contacts currently in an identity conflict state
When the system detects an identity conflict where contacts have inconsistent Customer IDs, the Export button shows an alert badge, and the menu also offers Export conflict contacts. If there are no conflicts at the moment, no action is needed.
Conflict list CSV columns
The CSV downloaded by Export conflict contacts contains all contacts "currently still in a conflict state," with the following columns:
| Column | Description |
|---|---|
| unified_contact_id (UCID) | Unified Contact ID |
| platform_type | Channel platform type (for example, line) |
| platform_name | Channel platform name (for example, the Official Account name) |
| external_member_id | External platform identifier |
| customer_id | The brand's custom customer identifier |
| conflict_reason | Reason for the conflict (for example, customer_id_multiple) |
👉 After obtaining the list, correct the incorrect Customer IDs or fill in the correct identifiers, then re-import: Tutorial | Import and Update Contact Data in MAAC. For how conflict detection works, see: Feature Description｜Contact Field Definitions and Matching Logic.
Example of exportable columns:
| Field name | Description |
|---|---|
| external_member_id | External platform identifier: may be a LINE UID, Facebook ID, or Instagram ID |
| name | Display name |
| phone | Contact phone |
| tags | Contact tags (comma-separated) |
| customer_id | Brand's custom contact ID |
| note | Note field |
| create_time | Creation time |
| last_update_time | Last update time |
| All custom fields | If you have created custom fields, they are included as well |
# How to Use Exported Data to Map Import Fields
The export file can serve as a reference and import template source for future contact updates. Note the following:
1. external_member_id mapping:
| external_member_id type | Mappable import Key | Notes |
|---|---|---|
| LINE UID | line_uid |
Recommended for updating LINE contacts |
| Facebook ID | Not supported | Facebook contacts cannot be imported yet |
| Instagram ID | Not supported | Instagram contacts cannot be imported yet |
2. How to format it for import:
Use the exported data, keep the following fields and edit the content as needed, then save it as a .csv file to update contacts:
line_uid (or phone / customer_id)
name / email / phone / note / tags
Custom fields (the field names must match the settings in the admin panel)
⚠️ If you use phone as the matching field, the system updates the contact with the later creation time
⚠️ Avoid leaving import fields blank—empty fields do not overwrite the original data
# FAQ
Q1: Why aren't the custom fields I created in the export file?
A: Confirm whether the field has been applied to the contact data; if it has no content, it will not appear in the export result.
Q2: Is external_member_id the same as line_uid?
A: Not necessarily. external_member_id is a unified field, and its actual content varies by source platform (LINE uses line_uid, Facebook uses fb_id, Instagram uses ig_id).
For more details, see: Tutorial | Import and Update Contact Data in MAAC