-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
Common questions and answers about xlmerg usage, especially for Vanta.com workflows.
A: xlmerg merges two Excel files intelligently - it takes your old file (with manual review entries) and a new file (fresh Vanta export) and combines them, preserving all your manual work while updating system data.
A: No! xlmerg runs entirely in your web browser. Just visit https://iinaveedahmed.github.io/xlmerg or download the HTML file.
A: Completely safe. xlmerg processes everything locally in your browser. No data is ever uploaded to servers or transmitted anywhere. It works offline too.
A: Excel files (.xlsx and .xls). The tool uses the first column (Account name) as the primary key for matching rows.
A: xlmerg is designed specifically for Vanta workflows:
- Upload your previous Vanta export (with completed manual reviews)
- Upload fresh Vanta export (with new users/tools/changes)
- xlmerg preserves all manual review data while updating system information
A: New employees are automatically added as new rows with blank review fields, ready for you to conduct access appropriateness reviews. No manual copying needed.
A: When Vanta detects new tools (like Slack, Datadog, etc.), xlmerg adds the entire new sheet or section with all accounts ready for review. Your existing reviews remain untouched.
A: xlmerg uses column name matching, so it automatically adapts to Vanta export format changes. New columns are added, renamed columns are mapped correctly.
A: Simple rules:
- Manual review data (conducted by, approved by, access decisions) → Always preserved from old file
- System data (roles, status, dates) → Updated from new Vanta export
- Blank cells in new file → Don't override old values
- New accounts → Added with blank review fields
A: These "orphaned" accounts are added to the bottom of the merged file and marked in the change log. This usually happens when employees leave or accounts are deactivated.
A: Yes! xlmerg maps columns by name, not position. If Vanta adds new columns or rearranges them, xlmerg handles it automatically.
A:
- System data conflicts → New file wins (more current)
- Manual data conflicts → Old file wins (preserves your work)
- Blank vs data → Data always wins (no overwriting with blanks)
A: xlmerg handles files up to 50MB efficiently. Typical Vanta exports (1000-5000 accounts) process in 10-30 seconds.
A: Currently optimized for desktop browsers. Mobile support is planned for future releases.
A: Currently processes one pair at a time. Batch processing is on the roadmap for future versions.
A: Check these items:
- File format must be .xlsx or .xls
- File size under 50MB
- File isn't password protected or corrupted
- Try refreshing the page and uploading again
A: Verify these items:
- First column contains Account name/unique identifier
- Both files have similar structure (account-based data)
- No special characters in sheet names
- Manual review data is in expected columns
A: This usually means:
- Files are identical (no system updates from Vanta)
- New file has no new accounts or role changes
- Changes are in excluded sheets
- Account names don't match between files (check spelling/formatting)
A: Try these solutions:
- Use Chrome or Firefox (best compatibility)
- Clear browser cache and reload
- Disable browser extensions temporarily
- Check browser console for specific error details
- Schedule: Run Vanta exports same day/time weekly
-
Naming: Use dates in filenames:
vanta_2025-01-22.xlsx - Review priority: Start with highlighted changes, then new accounts
- Documentation: Use "Changes made" column for audit notes
- Shared folders - Google Drive/SharePoint for team access
- Review assignment - Split new accounts among team members
- Approval workflow - Use "Review approved by" consistently
- Backup strategy - Keep previous weeks for audit trail
- Change documentation - Note why access was granted/revoked
- Reviewer attribution - Always fill "Review conducted by"
- Approval tracking - Document who approved decisions
- Date accuracy - Use consistent date formats
Traditional process: 5 hours/week × 52 weeks = 260 hours/year
xlmerg process: 2 hours/week × 52 weeks = 104 hours/year
Annual savings: 156 hours = ~4 weeks of work time
Security analyst salary: $75/hour
Annual time savings: 156 hours
Cost savings: $11,700/year per reviewer
Team of 3 reviewers: $35,100/year savings
- Zero data loss incidents (previously 2-3 per year)
- 100% review completeness (previously missed 5-10% of accounts)
- Faster audit preparation (days to hours)
- Improved compliance scores (complete change tracking)
If you have multiple Vanta environments (dev, staging, prod):
- Process each environment separately
- Use consistent naming:
vanta_prod_2025-01-22.xlsx - Maintain separate review cycles
- Aggregate for company-wide reporting
For organizations with custom Vanta connectors:
- xlmerg adapts to any column structure
- New integration data appears as new columns
- Manual mapping handled automatically
- Custom fields preserved across merges
- SOC2: Use xlmerg output for access review evidence
- ISO27001: Maintain required access documentation
- NIST: Support periodic access reviews
- Custom frameworks: Adapt change logs to requirements
- Getting Started - Basic setup and first merge
- Advanced Usage - Power user features
- Troubleshooting - Detailed problem solving
Still have questions? Ask in GitHub Discussions or create an issue.
© 2025 INATIQO PTY LTD - Empowering compliance teams worldwide