Guide

Checking customers and organizations after a JSM migration

Applies to Jira Service Management Cloud Contact support@asunoki.jp

After customers and organizations are moved into Jira Service Management Cloud — from another helpdesk, from another JSM site, or from Data Center — someone usually has to confirm that each customer landed in the right organization in each project. This guide shows a read-only way to do that check with Customer & Organization Export for JSM and a spreadsheet. The app does not move or fix data; it produces the list you compare.

01 Before you start

• The app is installed on the target Jira site by a site administrator (a free trial is available on the listing).
• The person doing the check has Service Management agent access to each project to be checked. The export only contains what that account can see, so use an account with the access the check needs.
• You have a list from the source system with at least an email address and an organization name for each customer.

02 Export the target project

1. In Jira, open Apps and select Customer & Organization Export for JSM.
2. Choose the migrated project and click Export CSV.
3. Note the counts shown when it finishes (Customers, Organizations, rows). They are useful for the summary of your check.

The file has one row per membership: Customer Name, Email, Organization Name, Organization ID. See Reading the CSV.

03 Compare with the source

1. Put both lists in one workbook, one sheet each. Lower-case and trim the email columns so the keys match.
2. Make a key of email|organization name in both sheets (for example =LOWER(TRIM(B2))&"|"&TRIM(C2)).
3. Look up each source key in the export (for example with XLOOKUP or COUNTIF), and each export key in the source.

Result	What it usually means
In the source, not in the export	The customer is missing from the project, is in a different organization, or the organization is not linked to this project. It can also be outside what the exporting account can see.
In the export, not in the source	An extra membership, for example a customer added during testing or a duplicate organization.
Export row with blank organization	The customer is in the project but in none of the organizations linked to it.
Same email, different organization names	Often a renamed or duplicated organization. Compare Organization IDs to tell them apart.

04 Fix, then export again

Make the corrections in Jira (or in your migration tooling), then export the project again and repeat the comparison until the differences are the ones you expect. Keep the final CSV with your migration sign-off if your process needs evidence.

05 Using the same check later

The same export works for a periodic review of who can raise requests in a project and for which organization, for example before reorganizing organizations or when offboarding a client.

06 What this check does not cover

• One project per export — repeat it for each project.
• It does not compare data for you, import data, or change anything in Jira.
• Only organizations linked to the selected project are listed, and only what the exporting account can see.
• Some endpoints the app uses are marked Experimental by Atlassian. See Limits.

07 Related documents

• Documentation
• Guide: what Jira exports natively, and when an app fits
• Privacy Policy
• Customer & Organization Export for JSM on the Atlassian Marketplace