Skip to content
Get a quote

Why do attachments fail when migrating to Zoho CRM?

Short answer

Usually the attachment mapping CSV names a file that isn't in the uploaded folder, which Zoho reports as "File Not Found". Other common causes: users weren't migrated first, the parent records weren't in the same migration, the zip has extra folders, or uploads exceed Zoho's size limits. Check the CSV against the folder before uploading.

By

What Zoho expects

In Zoho’s Migration Wizard, attachments are their own module. You upload the files in an attachments folder, plus a CSV that gives each file’s name and the ID of the record it belongs to. Zoho then matches every row of the CSV to a file in the folder and a record in the same migration. If either match fails, the attachment fails.

Causes and fixes

SymptomLikely causeFix
”File Not Found”The mapping CSV names a file that isn’t in the folder (wrong name, extension or case, or a subfolder path)Generate the list of files from the folder and compare it with the CSV before you upload
Upload fails before mappingExtra folders in the zip, or a changed layoutUpload the original folder structure (Data.zip) without extra folders
Attachments skipped, records fineThe user file wasn’t migrated first, so owners don’t resolveMigrate users.csv before the other modules, as Zoho’s FAQ says
Attachments not linked to anythingParent records weren’t in the same migration, or the IDs don’t matchPut parents and children in one migration, using the same migration IDs
Large sets fail part-wayOver 2 GB per file, 25 GB total, or a 10 GB / 200-CSV zipSplit into several migrations by module or date range
Migration pausedMore than 5,000 records in a module were skippedFix the source rows and resume

What the native tool does / where it stops

Zoho documents the error (“the attachment files are not found during migration”) and the fix (make sure the folder holds every attachment). It doesn’t help you build a correct mapping file from your old CRM. That’s where most failures start, because exports from systems like Salesforce don’t produce a file-to-record map in Zoho’s format. Salesforce Files, for example, link to records through a separate junction table.

Pre-flight checklist

  1. Count the files in the folder and the rows in the mapping CSV. The two numbers should match.
  2. Check that every parent ID in the mapping CSV exists in a module CSV.
  3. Check that file names match exactly, extension and case included.
  4. Migrate users first.
  5. Run one small module’s attachments first, then the rest.

Where FlitStack AI fits

FlitStack AI moves attachments with their records through the APIs, so no mapping CSV can drift out of sync. A sample run catches anything missing before the full run. See the Zoho CRM migration page.

Questions, answered

A few useful answers.

Can I add attachments after the records are already in Zoho?

Yes, but you need each record's Zoho ID or migration ID to link the file. That's easiest if you kept the source IDs on the records during the first migration.

Do API migrations from HubSpot bring attachments?

Zoho's HubSpot API migration doesn't list attachments or files among the mapped modules, so plan a separate attachment step.

Is there a per-attachment size limit?

Zoho's migration FAQ gives 2 GB per file and 25 GB in total, with zip uploads up to 10 GB or 200 CSV files. It doesn't state a separate per-attachment limit.

A closer look

Tell us what you’re moving.

Share your source, destination and rough record counts. We scope the migration and the process work with you and send you a quote.

Get a quote