import tasks from one cloud jira to another

[Ivan Andrieiev]

I need to import tasks from one cloud jira to another. I'm using the CSV import method, but I get an error with no explanation. Can anyone help?

[Evgenii]

Hi, @Ivan Andrieiev 

Welcome to Atlassian Community!

I wanted to ask - why you don't want to use builtin Atlassian functionality for data migration? It's much faster and easier than CSV. Go to Atlassian admin UI, select "Data Management" -> "Data Transfer", select required project and copy data from one instance to another.

[Marc -Devoteam-]

Hi @Ivan Andrieiev 

Can you share some more detail, like;

• Screenshot of the complete CSV
• Mapping of the columns on inport
• Log of the import

Are you importing on space level or using the system import option?

[C_Faysal _CFcon_]

Hey @Ivan Andrieiev 

To be totally honest i didn't ran lots of cloud-to-cloud data transfers but let me summarize some findings from the official docs here for you.

From what i've seen so far the "error with no explanation" almost always means the importer rejected rows but you're only seeing the summary screen. Two things first, then the usual root causes.

1. Get the real error. After the import finishes (even a failed one), the wizard shows a "Download a detailed log" link plus a downloadable file of the rows that failed. That log names the actual reason per row. That is where the explanation is hiding. Grab it before anything else.

2. Most common silent killers (Jira Cloud CSV import):

• Malformed CSV, the #1 cause. A row with more fields than the header, an unbalanced quote, or a comma/newline inside a value that isn't wrapped in quotes. Re-saving from Excel often breaks quoting. Open the file in a plain-text editor and confirm every field containing a comma or line break is enclosed in "...".
• Encoding: the importer expects UTF-8. A Latin-1/Windows-1252 file or a stray BOM throws it. Re-save explicitly as UTF-8.
• File too big: Atlassian's guidance is ~1500 work items per file (about 1h import). Bigger files get flaky. Split into batches.
• Missing/empty Summary: a Summary column is mandatory and every row needs a non-empty value, or the row is dropped.
• Date format mismatch: dates must match the format you set on step 2 of the wizard (Java SimpleDateFormat, e.g. dd/MMM/yy h:mm a). One off-format cell fails that row.
• User mapping: if the target site has external user management (Atlassian Guard/SSO) enabled, the importer cannot auto-create reporters/assignees. Map to existing email addresses or Account IDs, otherwise those rows fail.
  
  

Worth knowing for site-to-site specifically: CSV is a flat-data tool. It loses comments, attachments, issue history, issue links, and work-item rank. Since you're going Cloud to Cloud, the cleaner path is Atlassian's built-in cloud-to-cloud migration ("Transfer Jira data") / Jira Cloud Migration Assistant, which carries projects, users/groups, attachments, comments, and config that CSV drops. Use CSV only if you genuinely just need the issue rows.
Post the detailed-log error text and someone can pinpoint the exact line.

Sources:

• Import data from a CSV file (Jira Cloud)
• Transfer Jira data (cloud-to-cloud)
• What gets migrated with the Jira Cloud Migration Assistant

[Aaron Pavez _ServiceRocket_]

Hi @Ivan Andrieiev 

Can you share screenshots of the error?

And a screenshot of the CSV values and columns? just a couple of them. specially the columns.

Can you try by using only summary and description?

Do the work items exist in the destination cloud?

Regards