---
name: crm-architecture
description: "Design a maintainable CRM schema and migration plan from the business process. Use when the user requests crm architecture. Select relevant methods for the requested outcome; unrelated tasks do not require this skill."
metadata:
  version: "1.0.0"
---

# CRM Architecture

Design a maintainable CRM schema and migration plan from the business process.

## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts and required inputs. This generic package contains no client configuration. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for ownership, scheduling and completion. Preserve domain constraints; this Skill creates no competing execution path. Use one method, combine skills, or fill missing steps with authorized tools as the task requires.

External access uses the active Workspace’s approved Outloop capabilities. Never request, read, embed or expose credentials. A service named in a method is a possible dependency, not an access grant. Local file and application work uses the host’s authorized tools.

## Required inputs

- Current schema export
- Record lifecycle
- Ownership rules
- Required reports

## Methods

### Model entities

Draw entities and relationships before adding fields. Separate people, organizations, opportunities and activities rather than flattening repeated facts.

### Assign identity and ownership

Choose stable identifiers and deduplication keys. Document which system owns every synchronized field and how conflicts are resolved.

### Stage field migrations

For a field-type change, add a replacement field, backfill a small sample, compare values and dependent formulas, then stage migration. Do not remove the source field until rollback is possible.

### Trace representative records

Trace representative records through intake, qualification, handoff and closure. Verify permissions, automation triggers and reporting totals after any authorized change.

## Completion

Verify findings against source evidence and read back the resulting artifact or authorized change. Report inputs used, methods selected, output location, assumptions and unresolved dependencies. Do not report a plan, queue entry, draft, test fixture or accepted request as a completed external action. Use the task’s requested format; if a tool is unavailable, finish independent work and identify the exact unfulfilled deliverable.

## Test before relying on it

Read [the synthetic evaluation cases](references/evaluation.md) for activation, output and isolation checks. These cases are test instructions, not evidence that a host or provider test has passed.