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
| Symptom | Likely cause | Fix |
|---|---|---|
| ”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 mapping | Extra folders in the zip, or a changed layout | Upload the original folder structure (Data.zip) without extra folders |
| Attachments skipped, records fine | The user file wasn’t migrated first, so owners don’t resolve | Migrate users.csv before the other modules, as Zoho’s FAQ says |
| Attachments not linked to anything | Parent records weren’t in the same migration, or the IDs don’t match | Put parents and children in one migration, using the same migration IDs |
| Large sets fail part-way | Over 2 GB per file, 25 GB total, or a 10 GB / 200-CSV zip | Split into several migrations by module or date range |
| Migration paused | More than 5,000 records in a module were skipped | Fix 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
- Count the files in the folder and the rows in the mapping CSV. The two numbers should match.
- Check that every parent ID in the mapping CSV exists in a module CSV.
- Check that file names match exactly, extension and case included.
- Migrate users first.
- 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.