Suggested answer

Because the volume exceeds the Data Import Wizard limit, I would use Data Loader or a similar tool. I would clean and deduplicate the source data first, and store the legacy system's IDs in External ID fields on Account and Contact so I can relate records and rerun loads safely using upsert.

I would test a small sample in a sandbox, consider temporarily adjusting automation that would slow the load or send unwanted emails, and then validate record counts and sample records afterwards.

What interviewers look for

Interviewers want tool selection, External IDs, data cleansing, testing and post-load validation. A plus is mentioning load order (parents before children) and the impact of automation and sharing recalculation. A pitfall is loading straight into production without a test run.

Original practice content; not an official vendor answer. Verify details against current product documentation.

Community comments (0)

No comments yet.

Sign in or create a free account to add a comment. Comments are moderated before they appear.

Plain text only, 3–2000 characters. A moderator reviews every comment before it is published.