Choose only the columns and rows needed for the worksheet’s purpose, while retaining identity and report-required fields. The import preview is the place to check standard fields, available custom fields, ordering, and filter behavior before a data run.
Keep source identity with the worksheet
A display name helps people read a report. A source record ID identifies what the row represents. Keep source IDs when updates or future reconciliation are required. Do not replace a known record identity with a convenient name match.
Preserve object and account context too. A contact ID is not an opportunity ID, and a relationship field is not a substitute for the primary record’s own identity.
Use types rather than guessing
Numeric custom fields should retain numeric meaning; dates need a clear timezone and range; selection fields need their supported options. Treat a blank as missing information unless the source explicitly defines another meaning.
The field list distinguishes an empty catalog from missing access and load failures. A failed catalog request should not silently become “no custom fields.” Reconnect or retry while preserving the import draft.
Match filter scope to the question
Apply record filters before delivery when you need a limited dataset. Within a report, use the supported owner, period, pipeline, or calendar controls. Record-table filters affect the table in their stated scope and should not be mistaken for account-level permissions.
For date windows, review both the timezone and the metric’s date basis. A payment date and an opportunity-created date describe different events even when both appear in the same monthly dashboard.
Review changes before a new run
Column order can be changed using the available ordering controls. When fields or filters change, refresh the preview before Save & Run. A stale preview cannot validate the new dataset.
Import eligibility and outgoing-update eligibility are separate. A field that can be displayed in a worksheet is not automatically writable. Use the reviewed-update guide before planning any edits back to the CRM.
Related: data and availability · transfer pricing · all documentation