Back to the guide

Fictional import map: two jobs for one person

Every value and destination ID is fictional. This is not an account trial. Use the blank worksheet for your scope and observed results.

Scope and fields

Morgan owns a six-job migration from the immutable TAB-DEMO-v1 export. The trial contains the two jobs below. Phone is optional and empty. Person and deal each have a separate “Source ID” custom field.

Source Destination Value
Company Organization / Name Demo studio
Contact Person / Name Jamie Park
Email Person / Email [email protected]
Person ID Person / Source ID P-src-01
Job / Job ID Deal / Title and Source ID New website / J-src-01; website audit / J-src-02
Owner Deal / Owner Casey (an existing authorized user)
Next step Activity / Subject Review website inputs
Due date Activity / Due date October 12, 2026, date only
Task owner Activity / Owner Casey

J-src-01 and J-src-02 both refer to P-src-01. The activity belongs only to J-src-01. Notes and references remain in the attached source archive; this model has no attachments. Before the trial, the administrator checks permission, batch isolation, and the documented 48-hour import-revert option.

Expected lookup and reconciliation

Illustrative mapping: P-src-01 → CRM-P-201, J-src-01 → CRM-J-101, J-src-02 → CRM-J-102, activity → CRM-T-301. Both deals link to CRM-P-201; CRM-T-301 belongs to CRM-J-101. In this hypothetical result, five jobs are transferred, one uncertain identity awaits Morgan, and none is intentionally archived: 5 + 1 + 0 = 6. Do not import the sixth row until its identity is confirmed.

The illustrative cutover is October 12 at 4 p.m. America/New_York. Morgan reconciles final spreadsheet changes first. Casey uses their own account to open CRM-J-101 and CRM-J-102, comparing the person, owner and activity against the source. Actual outcomes, time and differences must still be recorded in the blank worksheet. A wrong relationship or missing task blocks the main import.