PRACTICAL GUIDE
CRM CSV import: prepare companies, contacts and opportunities carefully
Map the right fields, inspect duplicate matching and verify the planned result before applying a customer-data import. Start small and keep a reference copy for reconciliation.
A readable file is only the first requirement
A CSV can open correctly while still representing the wrong customer relationships. Before uploading, decide which rows are companies, contacts or opportunities and what identifies the same real-world record. Preserve an unchanged source copy and assign a reviewer who understands the data. This makes errors visible before a large import turns them into everyday operating problems.
Prepare one record type at a time
Tsumira’s CRM registers separate import targets for companies, contacts and opportunities. Contact fields include name, reading, phone, email, address and notes. Company and opportunity targets have their own fields. Do not assume that every column in an old workbook has a destination or that contact-to-company relationships are automatically completed by a contact import. Map and verify those associations independently where required.
- Remove explanatory rows and ambiguous mixed record types.
- Keep source identifiers in the reconciliation reference.
Inspect identity matching and field meaning
Contact matching uses available email, normalized phone or name with reading; company matching considers website, phone or name with reading. A shared mailbox or recycled phone can therefore require careful review. Missing Japanese readings can generate warnings rather than proving correct sorting. Opportunity amounts currently use whole JPY, so do not relabel EUR amounts as yen or treat an imported value as currency conversion.
- Review create, update and skipped outcomes on a sample.
- Resolve questionable matches with the data owner.
Review the plan, then reconcile the applied batch
The import flow separates preparation and application, with a batch record for the applied work. Inspect the plan and warnings before confirming changes. Afterward compare counts, representative fields and related opportunity references. An undo path exists for supported targets, but concurrently changed records are protected rather than blindly overwritten. Reversal still requires permission and review; it is not a substitute for checking the initial plan.
- Verify company and contact references on opportunities.
- Keep the source copy and batch reference for review.
A concrete workflow
Clean and classify
Separate companies, contacts and opportunities. Identify required values, doubtful identities and the person responsible for resolving them.
Map and inspect
Use a small representative sample. Review mapped fields, planned outcomes and warnings before applying any changes.
Apply and reconcile
Confirm the reviewed batch, inspect resulting records and document exceptions. Expand only after the sample behaves as expected.
An illustrative working example
Illustrative scenario: two contacts with a shared inbox
A customer file contains two people using the same central email address and different phone numbers. Because an email can participate in identity matching, the reviewer should examine the planned result instead of assuming two rows will always become two separate contacts. The sample also includes an opportunity referencing a company and contact. The final check verifies the actual associations and records any corrections needed.
Questions about this topic
Can I upload every old spreadsheet column?
Only mapped fields supported by the selected target have a verified meaning. Separate unsupported columns and preserve their original context rather than silently discarding important information or inventing a destination.
Does duplicate matching guarantee perfect identity?
No. Matching rules use the available identifiers. Shared emails, reused numbers and inconsistent names can need human review. Inspect the plan and resolve uncertain cases before application.
Can opportunity amounts contain other currencies?
The current opportunity amount field is whole JPY. Do not interpret a numeric import as currency conversion or proof of EUR support. Keep the original currency information and finance requirements separate.
Can an import always be undone without consequences?
Supported targets have an undo path, but permissions and concurrent changes matter. Protected later edits are not simply overwritten. Review the batch outcome and keep the original source for reconciliation.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
