Data Identity Model

What You Need to Know

We need your existing unique IDs for each record. That's it.

We'll handle the rest by creating a bridge between your IDs and our internal system.

Your IDs → Our System

What We Need From You

Provide the unique identifier you currently use for each record in your system:

• Associations: Your association ID (e.g., A-12345)
• Units: Your unit ID (e.g., U-67890)
• Members: Your person/member ID (e.g., M-54321)
• Accounts: Your account ID (e.g., ACC-9999)

Important: These IDs must be unique within each entity type.

What We Do

1. Store your ID as the External ID
2. Generate a permanent UUID for internal use
3. Create a bridge so updates always match the right record

How the Bridge Works

Your Record          →  Bridge  →  Our System
─────────────────────────────────────────────
Association A-12345  →  Maps to →  UUID: abc-123...
Unit U-67890         →  Maps to →  UUID: def-456...

When you send us data:

• First time: We create a new record and generate a UUID
• Updates: We match your ID and update the existing record
• No duplicates: Same External ID = same record, always

Example

Your CSV includes:

association_id,name
A-12345,Sunset Hills HOA

We create:

{
  "external_id": "A-12345",  // Your ID (the bridge)
  "uuid": "550e8400-...",    // Our internal ID
  "name": "Sunset Hills HOA"
}

Later you update:

association_id,name
A-12345,Sunset Hills Community

We update the same record:

{
  "external_id": "A-12345",      // Same bridge ID
  "uuid": "550e8400-...",        // Same UUID
  "name": "Sunset Hills Community"  // Updated name
}

Requirements

✅ Your IDs must be unique within each entity type ✅ Your IDs must be consistent across all files ✅ Your IDs should be strings (letters, numbers, dashes, etc.)

❌ Don't change IDs between submissions ❌ Don't reuse IDs for different records ❌ Don't worry about our internal UUIDs

Quick Reference

That's It

Just give us your IDs. We'll handle the mapping, prevent duplicates, and keep everything in sync.