NextAutomation: commercial property import mapping exercise
Prepared November 8, 2026. All records and identifiers are synthetic.
Vendor-neutral staging files, not a production-ready CRM upload or connector.

staging.csv contains 4 observations, 3 property IDs and 2 entity IDs.
R-04 holds an unresolved contact proposal. Do not create a person.
Expected distinct outputs: 3 properties, 2 entities, 3 property/entity associations, 0 people.
Shared mailing address does not merge E-01 and E-02.
A repeated authorized sandbox import should preserve those counts and associations under the chosen mapping.

Before adapting:
1. Confirm destination object model, identifier and association rules, blank-value behavior and permissions.
2. Map to destination fields and any existing destination IDs; preserve source batch and source-row IDs.
3. Test in a sandbox or explicitly authorized test destination.
4. Inspect records AND associations; repeat the same batch and compare by stable key.
5. Preserve before/after evidence and agree a correction procedure before a real import.
6. Retain licensing, confidentiality and contact-use restrictions. No resale rights are granted.
These files contain no executable importer and make no claim of a tested third-party connector.