Contact Import

Upload contacts, map fields, catch duplicates, and review import errors before data enters the CRM. The screen connects Upload and Map fields so sales teams can find the “Upload CSV” action while checking rows found and mapped fields.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Email → Email and Company → Account, rather than an empty visual shell.

Use this template in Figr

Template facts

Screen

Form

Primary action

Upload CSV

Pattern

Form

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Sales teams need a clear “Upload CSV” action without losing sight of rows found, mapped fields and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

Primary action: Upload CSV is clearly available where the task happens.
Main view: Upload keeps the starting point obvious.
Connected view: Map fields supplies nearby context.
Metric: Rows found is visible with a meaningful value.
Another signal: Mapped fields helps people judge what to do next.
Representative record: Email → Email makes the example specific.
Second record: Company → Account shows the pattern works beyond one item.

States worth designing

Missing required details; show what people can do instead of leaving a blank panel.
Loading upload without changing the layout unexpectedly.
Invalid or conflicting entry; explain the problem and preserve work.
Permission denied for map fields; clarify who can continue.
Success after choosing Upload CSV; confirm the result and the next step.
Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Upload → Map fields → Upload CSV → Review outcome

Patterns used

Form, Upload, Map fields, Duplicates, accessible states, contextual actions

Why these choices work

Put requirements beside each field and show validation near the source of the error. Keep entered details if saving fails.

In this design, people should be able to compare Email → Email with Company → Account. Make rows found clear, then use mapped fields to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Upload CSV” action. The happy path alone is not enough.

Related UI examples: Account Detail, Sales Forecasting, Deal Pipeline.

Start from this in Figr

Design a contact import screen for our existing software product. Use our real design-system tokens, components and product language. Show Upload and Map fields, include believable records such as Email → Email, and make upload csv easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr