Membership is a lifecycle, not a list

A useful membership record explains who the member is, which organization relationship it belongs to, its current standing, the effective dates and level, payments or adjustments, benefits, and the evidence behind any manual change.

Crafted Call includes membership standing badges and record linking so staff can see relationship context across the workspace. Entitlements and permissions still control who can view or change membership and financial data.

Define the system of record

Before connecting Little Green Light, decide which system is authoritative for identity, postal and email details, membership level, start and end dates, standing, gift history, and communication preferences. A synchronization is not governance. Write down the direction for every field.

Match cautiously

Use stable external identifiers when possible. Email address alone is not a safe unique identity: households share addresses, people change addresses, and duplicates exist. Separate exact matches, probable matches requiring review, and new records. Never silently merge two people because their names look similar.

Understand the sync boundary

Crafted Call's Little Green Light integration includes membership synchronization in addition to contact and relationship workflows. Confirm the configured direction, included fields, schedule, permissions, and organization plan before enabling it.

For each run, retain counts for read, created, updated, skipped, conflicted, and failed records. Surface field-level exceptions without placing sensitive data in logs. A retry must not create duplicate members or reverse a staff-approved correction.

Reconcile standing and benefits

Test renewals, lapsed and reinstated memberships, household relationships, refunds, complimentary terms, changed levels, and manual exceptions. Verify that member pricing or benefits use the intended effective date and standing, not merely the presence of a linked record.

Member roster CSV import is implemented in controlled rollout, so access varies by organization. When available, treat an import as a staged reconciliation: validate headers and dates, preview creates and updates, isolate ambiguous matches, and keep an error report.

Operate the connection

Assign an integration owner and a membership owner. Review failures on a schedule, document conflict decisions, rotate credentials, and retest after changing field mappings or membership policy. Before disconnecting, export unresolved exceptions and state which system will remain authoritative.