Do it in this order and you'll avoid 90% of the duplication pain:
- Drive first - your Confluence exports are the most structured. Smart Import will generate manifests for them and set the topic vocabulary
- Notion second - runbooks usually reference the same entities. Jarvis will detect overlap via the relationship graph and merge context, not duplicate files
- Email history last - noisy by nature. Filter by date range (12 months is usually enough) and by the labels your team uses for resolved tickets
One thing to watch: after step 1, give it 5 minutes before kicking off step 2. The manifest generator is what lets Jarvis detect overlap, and it runs async after import.
Docs on the full flow: https://docs.deskclone.ai/smart-import