Workspace initialization

Settings → Initialization (under BILLING & DATA) groups advanced admin utilities into Organization and Financial Operations tabs. Use these tools during staff transitions, ledger cleanup, or payment ID standardization — not for day-to-day configuration. See Settings overview for safer first-time setup paths. Confirm bank accounts under Payment settings and plan entitlements in Billing and subscription before running financial migrations.

Organization tab

Ownership transfer

Reassign CRM records from inactive or removed users to active team members:

1. Transfer From — Select an inactive or removed member; a preview counts deals, contacts, and activities
2. Transfer To — Choose an active member (enabled only when the preview total is greater than zero)
3. Process Transfer — Confirm in the dialog; action is irreversible

The tool moves deals, customers, and activities — not payment ledger rows (use Financial Operations for those).

Tasks from removed users

Lists incomplete tasks created by removed or deactivated users, broken down by person. Mark all as done completes them in bulk after confirmation — useful when offboarding leaves open task noise.

Please note:

• Ownership transfer cannot be undone; verify the preview counts before confirming.
• Marking tasks done is permanent — export or reassign important work first.

Financial Operations tab

Payment transaction ID format

Customize how payment reference IDs are generated:

Variable	Meaning
{yyyy}	Four-digit year
{mm}	Two-digit month
{dd}	Two-digit day
{seq:N}	Sequence padded to N digits (e.g. {seq:4} → 0001)

Default pattern: PAY-{yyyy}{mm}-{seq:4}.

Set Sequence reset period to daily, monthly, or yearly. Click Save to persist; only future payments use the new pattern unless you run Regenerate Past IDs.

Regenerate Past IDs rewrites all existing payment transactionId values to match the current format, recalculated chronologically. This may break external references or printed documents — use only after finance sign-off.

Account transaction migration

Move ledger entries between internal bank accounts (requires at least two active accounts from Payment settings):

1. Launch Migration Tool
2. Select source and target accounts
3. Optionally exclude expenses and/or deposits
4. Review the transaction count preview
5. Migrate Transactions — irreversible

Use when merging duplicate bank entries or consolidating petty cash logs. This updates payment records, not CRM ownership.

flowchart TB
  subgraph Org[Organization]
    OT[Ownership transfer]
    TK[Mark removed-user tasks done]
  end
  subgraph Fin[Financial Operations]
    ID[Payment ID format]
    MG[Account transaction migration]
  end
  OT --> CRM[Deals, customers, activities]
  MG --> Ledger[Payment ledger entries]
  ID --> Future[New payment IDs]
  ID --> Regen[Optional regenerate all IDs]

Permissions

Permission	Typical use
settings.view	Open Initialization
settings.update	Save ID format, run transfers and migrations
payments.read	Understand migration impact on ledger

Admin-only API routes enforce destructive actions server-side.

Related articles

• Bank accounts before migration: Payment settings
• Subscription limits and add-ons: Billing and subscription
• Role and access alignment: Roles, permissions, and RBAC
• Day-one workspace setup: Configure your workspace