Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Sales CRM · Feature guide

Resolve import errors and retry safely

Use stable references and row results to recover from conflicts or partial completion without duplicating deals.

Audience: authorised staffPermission: View access and Create dealsReviewed 30 October 2026
Where to goSales CRM → Import & export → Choose and review CSV → Review file or Import results

Before you start

Use your own authorised staff account in the intended Britixo workspace. The Sales CRM module must be available and your role must include the permissions stated above. Existing leads, customers, communications and customer portal pages retain their normal access rules.

Follow these steps

  1. Read Invalid messages during review and correct those rows before starting the import. No new deal is created by Review file.
  2. After creation, review each row: Created identifies a new deal, Existing identifies a previously imported deal preserved by this account, and Failed identifies a row that could not be saved.
  3. Select Download row results to retain references, titles, result states, deal IDs and messages. The result file is a report, not an import template.
  4. Retry failed or uncertain rows with the same account, external references, original data and defaults. Previously completed references are recognised.
  5. If the same reference has conflicting data, open the existing deal and make an authorised normal edit. Do not change its external key merely to bypass the conflict.

Behavior and limits

  • Reference tracking is per importing staff account. A different account has a separate import reference history and can create another record using the same external key. Coordinate the importing account for a migration.
  • A previously imported reference with matching original data returns the existing deal without overwriting subsequent edits.
  • The same reference with different import data or defaults is rejected. Changes to omitted defaults, including a stage’s default probability, can make a retry differ; retain the intended original values explicitly.
  • The same deal title is a review warning, not a universal duplicate identity. Different opportunities may legitimately share a title.
  • Each row is saved separately. Rows successfully created before another row fails remain available. Repeating the same references is the recovery mechanism.
  • A stale session, changed permissions or changed stage/field configuration can invalidate a row between preview and creation. Review the current rules before retrying.

Check it worked

  • After retrying, confirm the expected records show Existing rather than another Created result.
  • Compare the displayed deal ID with the original successful result and confirm later edits were preserved.

Troubleshooting

  • If a previously imported deal is no longer visible to your account, the import cannot reveal or edit it. An authorised manager should review ownership and access.
  • A validation failure for one row should be corrected at its source. Keep the successful rows’ references unchanged.
  • If the browser lost the result screen, review the same file again. Existing references help identify completed work without relying on the missing response.