Excel migration guide
Prepare your data for an Excel migration pilot
A workbook row is not always a separate application. People may appear on several sheets, colours may represent stages and notes may describe conversations. Begin by agreeing what these details mean with your team.
iyely Visa exports the application list as CSV. This differs from automatically importing spreadsheet rows into CRM records. Confirm a method for your files before making bulk import an assumption in your plan.
Describe the meaning of each spreadsheet field
Keep an unchanged source copy. List column names, data types and owners. Review application details, adviser, branch, stage, conversation notes and document links separately; avoid forcing mixed cell contents into an unrelated field.
- Check whether similar records actually represent the same case; do not merge on name alone.
- Make telephone and date formats consistent; do not guess an unclear value.
- Translate colour-coded statuses into explicit stage names agreed by the team.
- Check which case a document link belongs to and who can access the underlying file.
Pilot six fictional records
Include exceptions in the sample
Prepare six synthetic rows with similar names, an unclear call date and a document awaiting revision. Do not attach real client data to a public trial exercise or demo request.
Check the existing screens
Create the small sample through the application entry screens. Select the appropriate branch and adviser; record the document and follow-up task in their own places. Uploading an xlsx file as a document does not turn its rows into applications.
Compare counts and meaning
Compare the pilot list with the CRM records. Is anything missing, duplicated or matched incorrectly? Do stage, adviser and next action agree with the preparation plan? Resolve errors before expanding the scope.
Agree one current working location for the team
Agree when and where new work will be recorded. Independent spreadsheet and CRM updates create competing current states. Assign a reviewer, maintain an exception list and define when to pause. Retain the source copy while discrepancies remain.
Compare record counts, document volume and workspace needs with current plan limits. Discuss the scope of any bulk migration, archive transfer or historical data work in advance. Do not treat a CSV export as a complete backup of documents, versions and activity history.
Frequently asked questions
Will uploading an Excel file automatically create applications?
This guide does not promise that capability. Document upload, CSV export and record import are different operations. Confirm an appropriate migration method for your files separately.
When should we stop using the old spreadsheet?
Decide after the pilot and team checks establish a current working location. Manage access to and retention of the earlier copy under your office's data management decisions.
Clarify a small migration scenario first
Try the workflow using your field list and a synthetic sample. Include questions about migration methods in your demo request.