CoreSwift CRM

Login to CoreSwift CRM

Navigate to:

https://coreswiftcrm.com

Enter your email and password.

On success, you receive a JWT access token and refresh token. The app stores these for all API calls. You'll be redirected to the Dashboard.

Navigation

API Overview

All endpoints sit under /api/:

• Public: auth/login, auth/register, auth/forgot-password, auth/reset-password
• Protected: All others require Authorization: Bearer <token>

Stats Cards

At-a-glance CRM metrics for your own account, fetched via GET /api/dashboard/stats. Every counter is scoped to the account in the token.

GET /api/dashboard/stats
Authorization: Bearer <token>

Response:
{
  "total_contacts": 42,
  "total_companies": 15,
  "total_opportunities": 28,
  "total_revenue": 5000.00
}

total_contacts, total_companies and total_opportunities are row counts for your account. total_revenue is money, not a count: it is the sum of opportunities.value over the opportunities you have marked won, and 0 when you have none. These four are the whole response — no other key is returned.

Pipeline Summary

Below the stats cards, each active pipeline shows opportunity counts per stage, giving a visual funnel of where deals are concentrated. Default pipelines are highlighted.

Global Search

Search all entities at once:

GET /api/dashboard/search/query?q=david

Matches across contacts (first name, last name, full name, email, phone), companies (name/email), and opportunities (name). Returns top 10 per type, and only from your own account.

GET /api/dashboard/search/query?q=david
Authorization: Bearer ***

Response:
{
  "query": "david",
  "total_contacts": 42,
  "total_companies": 15,
  "contacts": [
    { "id": "1f0c...", "first_name": "David", "last_name": "Giraudy", "email": "david@example.com", "phone": "+13055550100" }
  ],
  "companies": [
    { "id": "9a24...", "name": "Acme Corp", "email": "info@acme.example" }
  ],
  "opportunities": [
    { "id": "77c1...", "name": "David renewal", "value": 12000.00, "is_won": false }
  ]
}

total_contacts and total_companies are your own row totals — the same numbers as GET /api/dashboard/stats — and not the number of matches; the matches are the three arrays. A request with no q (or a blank one) returns those totals with three empty arrays, and so does a query that matches nothing.

Contact Fields

Adding a Contact

POST /api/contacts
Authorization: Bearer <token>
Content-Type: application/json

{
  "first_name": "John",
  "last_name": "Doe",
  "email": "john@example.com",
  "phone": "+1234567890",
  "company": "Acme Corp",
  "source": "Website"
}

Edit, Delete & Search

• Edit The row's Edit button → PATCH /api/contacts/:id
• Delete Soft delete by API only (DELETE /api/contacts/:id) — a contact row has no delete control
• View / edit Every row carries an Edit and a Tags button; there is no contact detail page
• Search GET /api/contacts/search?q=john (name/email/phone)

Assigning Tags

Lead Scoring

Score rules fire automatically:

Finding Duplicate Contacts

Over time the same person can end up in your workspace more than once — imported from a spreadsheet on Monday, added by hand on Friday. The Duplicates screen (in the sidebar, directly under Contacts) shows you every set of records that look like the same person so you can decide what to keep.

It compares two things:

• The same phone number, once punctuation and spacing are ignored — (561) 555-0143 and 5615550143 count as the same number.
• The same first and last name, once case and extra spaces are ignored.

Email addresses are deliberately not compared: a workspace can never hold two active contacts with the same email address, so a report on email could only ever come back empty.

Nothing is merged automatically. Each row has an Edit button that opens that contact in the normal editor, so you decide which record survives and what it says. If a group names a record you cannot see in the list above it, the record is still there — the name lookup stops after 500 contacts, and the screen says so rather than pretending the contact is missing.

If you see "Account matching is not available on your current plan", the report is switched on for paid plans only. The screen tells you that instead of showing an empty list, because "you have no duplicates" and "you are not allowed to look" are different answers.

GET /api/account-match/duplicates?limit=25
Authorization: Bearer ***

{
  "groups": [
    { "kind": "phone", "key": "5615550143", "count": 2,
      "contact_ids": ["6b5f8ccc-…", "cd67aebd-…"] }
  ],
  "total_groups": 1,
  "contacts_in_groups": 2
}

Company Fields

Managing Companies

POST /api/companies
Content-Type: application/json

{ "name": "Acme Corp", "industry": "Technology", "size": "51-200" }

Companies & Opportunities

Link a company to an opportunity via company_id to track all deals per organization.

Understanding Pipelines

A Pipeline is a sales process composed of sequential Stages. Opportunities move through these stages toward close.

Sales Pipeline Stages

Client Onboarding Stages

Creating a Pipeline

POST /api/pipelines
Authorization: Bearer <token>

{ "name": "Support Pipeline", "description": "Support lifecycle", "is_default": false }

Stage Configuration

Each stage supports:

• Name Display label
• Color Hex color (e.g. #3B82F6)
• Sort Order Integer position
• Probability Win % (0-100)
• is_won Mark as closed-won stage
• is_lost Mark as closed-lost stage

What is an Opportunity?

An Opportunity (deal/tracker) represents a potential sale or business outcome progressing through a pipeline. Each opportunity is tied to a specific pipeline and stage.

Creating an Opportunity

POST /api/pipelines/:pipeline_id/opportunities
Authorization: Bearer ***

{
  "stage_id": "uuid-of-stage",
  "name": "Enterprise Deal - Acme Corp",
  "value": 50000.0,
  "currency": "USD",
  "probability": 60,
  "expected_close_date": "2026-08-15",
  "contact_id": "uuid-of-contact",
  "company_id": "uuid-of-company",
  "source": "Referral",
  "notes": "Initial call went well"
}

Moving Deals Through the Pipeline

To advance an opportunity to the next stage:

• Drag-and-drop Drag an opportunity card from one stage column to another
• Change stage dropdown Use the stage selector on the deal card in its stage column

Both actions use:

PATCH /api/pipelines/:pipeline_id/stages/:stage_id/move/:opportunity_id
Authorization: Bearer ***

{ "stage_id": "uuid-of-next-stage" }

Value, probability, expected close date and notes are updated with PATCH /api/pipelines/:pipeline_id/opportunities/:id.

Winning & Losing Deals

When a deal reaches a Won or Lost stage, CoreSwift automatically sets the corresponding boolean flags:

• Won: is_won = true adds value to the "Won Deal Value" dashboard stat
• Lost: is_lost = true optionally record a lost_reason for analysis

Opportunity Analytics

The dashboard carries three of these tiles, each read from GET /api/dashboard/stats:

• Opportunities Opportunity count for the account
• Won Deal Value Won opportunity value
• Pipelines Number of pipelines

Per-stage counts are not shown anywhere.

Sales Group Overview

The sidebar's Sales group holds one screen, Pipelines & Deals (each pipeline's cards are its deals/opportunities). Contacts is a top-level sidebar item of its own, and Companies has no sidebar entry — open it with g then o. The group is collapsed by default — click Sales to expand it.

Contacts

Contact management with search (/api/contacts, GET /api/contacts/search), pagination (50 rows per page by default) and add/edit dialogs. A contact has no status field and the list has no status column.

GET /api/contacts
POST /api/contacts
PATCH /api/contacts/:id

Companies

Track organizations with name, domain, industry, and contact count. Searchable and paginated.

GET /api/companies
POST /api/companies
PATCH /api/companies/:id

Pipelines & Deals

Manage sales pipelines with custom stages. Track deals through pipeline stages with value, probability, and stage tracking.

GET /api/pipelines
POST /api/pipelines
GET /api/pipelines/:pipeline_id/opportunities
POST /api/pipelines/:pipeline_id/opportunities

Marketing Group Overview

Contains Campaigns, Lists and Analytics. Expand it by clicking Marketing in the sidebar.

Campaigns

Create and manage marketing campaigns. Each campaign has a type (email, SMS, multi-channel), status (draft/active), and sent count. Activate campaigns from the list view.

GET /api/campaigns
POST /api/campaigns
PATCH /api/campaigns/:id
POST /api/campaigns/:id/activate
POST /api/campaigns/:id/pause

Email Sequences

Build automated email sequences with multiple steps. Each sequence can have triggers, enrollments, and step-based delays. There is no separate Email Sequences screen — sequences are campaign records, managed under Marketing > Campaigns.

GET /api/campaigns
GET /api/campaigns/:id               (includes steps)
GET /api/campaigns/:id/enrollments   (view enrolled contacts)

Automation Rules

Create trigger-based automation rules. Configure triggers (tag added, score changes, list membership changes) and actions (add/remove tag, move stage, add/remove from list). Each rule has a trigger config and action config stored as JSON.

Available triggers: tag_added, score_change, list_added, deal_stage

Available actions: add_tag, remove_tag, move_stage, add_to_list, remove_from_list

GET /api/automation/rules
POST /api/automation/rules
PATCH /api/automation/rules/:id
DELETE /api/automation/rules/:id

Checklists

Define checklist templates with stages for onboarding and process management. Each stage has an order, title, optional message template reference, and delay in hours. View instances and track progress.

GET /api/checklists/templates
POST /api/checklists/templates
PATCH /api/checklists/templates/:id
DELETE /api/checklists/templates/:id
GET /api/checklists/instances

Where these live

There is no Operations group in the sidebar. The recorded event feed is API-only; portfolio companies are managed in the platform console under Portfolio Companies; lists live under Marketing > Lists.

Events

Logged system events — each with its type, description, related entity and date — are read through the API. There is no Events screen in the console.

GET /api/events

Portfolio

View all portfolio companies across your user ecosystem. Searchable by name, slug, or domain. Shows status, plan assignment, and active/inactive state.

GET /api/portfolio

Your company’s login

If the CoreSwift team set your company up, your workspace and your owner login were created together, and the login details were emailed to the address on the company record. Sign in with that password, then change it in Settings → Change password. If no email arrived, use Forgot password? on the sign-in page — that sends a fresh link to the same address.

Call Records

Telnyx call records — caller, called number, duration, disposition, cost and timestamp — are stored for billing and audit. There is no Call Logs screen in the CRM and no endpoint that lists them, so they are not shown in the app today.

Lists

Create and manage contact lists. Each list shows member count and can be used for campaign targeting. View members inline from the list detail.

GET /api/lists
POST /api/lists
PATCH /api/lists/:id
DELETE /api/lists/:id
GET /api/lists/:id/members
POST /api/lists/:id/members

Your Help Desk — Built In

CoreSwift CRM includes a complete customer support ticketing system. Replace Freshdesk, Zendesk, or your overloaded email inbox. Your customers submit requests. Your team manages them. Nothing leaves the platform.

No API keys. No chatbot plugins. No external subscriptions. It just works.

How Tickets Come In

Tickets can arrive through multiple channels — all tracked by source so you know where every request came from:

None of these channels is privileged. A ticket created by your chatbot, your contact form, or your staff member is treated identically. No special routing, no hidden costs.

Embed Widget — One Line on Your Website

Add a floating support button to any website with one script tag:

<script src="https://coreswiftcrm.com/s/YOUR_TENANT_ID/widget.js"></script>

That gives you:

• Floating button — bottom-right corner, matches your brand
• Slide-out form — name, email, subject, description, priority
• Success confirmation — visitor knows their request was received
• No dependencies — vanilla JS, no framework, no CORS issues
• No login required — your visitors submit tickets without accounts

Admin Support Panel

Your team manages everything from 🎫 Support in the sidebar:

• Full queue — all tickets, filterable by status and priority
• Create tickets — manually open tickets during phone calls
• Reply inline — threaded messages on every ticket
• Status workflow — open → in progress → resolved → closed
• Priority levels — low, medium, high, urgent
• Assignment — route tickets to team members

Customer Portal

Your end customers open 💬 My Support and see only their own requests. The portal lives at /s/<your-tenant-id>/support, and your team can open it from Support Tickets → 💬 My Support.

There is no password to issue and no email needed to sign in: the customer enters their email address plus the reference of a request they already have (the first 8 characters of the ticket id, shown on the ticket in your console). That pair proves the address, and the server hands back an access grant that never travels in a URL.

• Submit new requests — with priority selection
• View their history — all past tickets, statuses visible
• Reply to open tickets — threaded conversation with your team; replying to a resolved request reopens it
• Tenant-scoped — customers only see their own data, never another customer's and never another tenant's

This is their personal help desk — not your admin panel. They manage their own support experience.

API for Integrations

For programmatic access — connecting chatbots, Zapier, custom apps:

POST /s/:tenant_id/ticket
GET  /s/:tenant_id/widget.js
POST /api/public/contact

Set source: "agent" when creating tickets from chatbots or AI systems. The public endpoints require no authentication — designed for third-party consumption.

Automation Group Overview

The Automation group (sidebar icon ⚡) contains Rules, Tags and Lead Scoring. The strategy-engine screens this section used to name are not in the console; each card below says what is API-only instead.

Agency Sequences

There is no Agency Sequences screen. Rules are read through GET /api/automation/rules; the Rules screen under Automation is the rule UI.

GET /api/automation/rules

Directory Onboarding

There is no Directory Onboarding screen. Checklist instances (entity, stage, progress, start date) are rendered on the Checklists screen under Workflow and read through GET /api/checklists/instances.

GET /api/checklists/instances

Health Monitor

Account health is computed by the API: POST /api/monitoring/account-health/check runs an analysis and GET /api/monitoring/health reads it. In the console, the platform-admin Monitoring screen renders those endpoints; there is no "Run Health Check" button in the tenant workspace.

POST /api/monitoring/account-health/check
GET /api/monitoring/health

Message Templates

Create reusable message templates for email and SMS communications. Each template has a name, channel, subject and body. Manage them in the console under Communication > Email Templates.

GET /api/comms/templates
POST /api/comms/templates
PATCH /api/comms/templates/:id
DELETE /api/comms/templates/:id

Nurture Campaigns

Contact enrollments are read through GET /api/campaigns/:id/enrollments. There is no Nurture Campaigns screen; the campaigns themselves are managed under Marketing > Campaigns.

GET /api/campaigns/:id/enrollments

Site Configuration (Platform Admin)

General details, SEO/meta (title, description, keywords, Open Graph) and branding colours are edited in the platform console under Admin Settings > Configuration ("Site Configuration"), which reads and writes GET/PUT /api/admin/site — server-side, not in the browser. The tenant workspace has no Settings page of its own.

Platform Console (Platform Admin Only)

Entries below the ── ADMIN ── divider appear only for a user the server marks as a platform admin (users.is_platform_admin, carried in the session as platform_admin). A tenant owner/admin role is not platform authority. The entries are:

• Users — Every user on the platform with the workspace they belong to (read-only list).
• Revenue > Billing & Plans — Subscription plans, pricing and limits.
• Platform > Webhooks — a pointer to where outbound webhook endpoints are configured: each workspace registers its own in the workspace console under Settings > Webhooks (Enterprise plans). The routes are workspace-scoped, so this console has no editor for another workspace's endpoints. Also Widgets, Native Apps, Audit Log, Monitoring.
• Communication Admin > Telnyx Admin and Private Email Admin.
• Modules & Plans — the module registry: switch modules and individual features on or off per plan, and override a single workspace.
• Admin Settings > Configuration — site configuration (SEO, legal pages, homepage).

There is no Impersonate button in the console: the API can start and stop impersonation, but no screen calls it.

Admin: Users & Workspaces

People live on the Users screen — every workspace's users in one list with name, email, role and joined date.

GET /api/admin/users
GET /api/admin/tenants

Admin: Plans & Feature Overrides

Modules & Plans is where each plan's modules and individual features are switched on, and where a single workspace can be granted or denied one feature without touching its plan. Enter a workspace id to load the features it effectively gets, then tick one to override it.

GET /api/admin/modules
POST /api/admin/plans/:slug/modules
POST /api/admin/plans/:slug/features
GET /api/admin/tenants/:id/entitlements
POST /api/admin/tenants/:id/overrides

Admin: Plans & Features

Plans control what features users can access. Each plan has:

• Pricing: Monthly and yearly price, with optional payment link
• Limits: Max contacts, deals, and users (set to -1 for unlimited)
• Feature Toggles: the boolean flags of the module registry (the live list is here)

Available features are not a fixed list: they are the boolean flags in the module registry (modules / module_features) — the same switches the Modules & Plans panel renders. See Plans & Feature Access for the flags live today.

GET /api/billing/plans
POST /api/billing/plans
PATCH /api/billing/plans/:id
DELETE /api/billing/plans/:id
GET /api/billing/features

Admin: Telnyx Configuration (API only)

Telnyx provider settings are read and written through the API: GET /api/telnyx/config, PUT /api/telnyx/config, and GET /api/telnyx/available for the phone numbers on the account. The console's Telnyx Admin entry (Communication Admin group) is a placeholder screen today, so there is no form to paste the key into.

GET /api/telnyx/config
PUT /api/telnyx/config
GET /api/telnyx/available

Admin: Impersonation

The platform-admin API can start and stop impersonation, but the admin console has no Impersonate button yet — no screen calls it.

Free Access & Upgrades

CoreSwift CRM offers free access with a limited feature set. When your plan does not cover something, the console shows an upgrade banner whose Upgrade Now button opens the plan comparison. Each tier that is not your current one carries a Request this plan button: pressing it sends the request to our team (nothing is charged, and no plan changes by itself) and the request names your workspace and the address to answer. Putting the workspace on a plan is therefore still an operator action — self-service checkout is not open on this install — but asking is now one press inside the app instead of a support email you had to compose yourself. Feature availability is determined by your plan's feature flags. A tier that carries a payment page also shows Open payment page: it opens that page, and pressing it files the same request first, so our team knows which workspace is paying (nothing is charged by this app).

Tags Overview

Tags are colored labels used to categorize contacts and companies. They support filtering, segmentation, and reporting.

Managing Tags

POST /api/tags
Content-Type: application/json

{ "name": "VIP", "color": "#F59E0B", "category_id": "optional-uuid" }

Tag Categories

Tag Categories group related tags together. Categories don't affect functionality but help organize large numbers of tags. Each tag can belong to one category or none.

Lists Overview

Lists are saved groups of contacts for targeted campaigns, email sends, or segmentation.

Default pre-seeded lists:

• Newsletter Subscribers (static)
• Cold Leads (dynamic low score)
• Hot Leads (dynamic high score)
• Retargeting Audience (dynamic)

Managing Lists

POST /api/lists
Content-Type: application/json

{ "name": "Q3 Campaign", "list_type": "static", "description": "Targets for Q3 email blast" }

POST /api/lists/:id/members
{ "contact_id": "uuid-of-contact" }

Webhook Overview

CoreSwift CRM supports both incoming and outgoing webhooks for integration with satellite apps and external systems.

Inbound Webhooks (Receiving Data)

Other apps can send events to CoreSwift using authenticated webhook endpoints. The URL carries only the key prefix, which is a public index; the credential is the full key in the X-Satellite-Key header, and its SHA-256 digest must equal the digest stored for that prefix. A missing header or a wrong key is refused with 401.

POST /inbound/:key_prefix/:event_type
X-Satellite-Key: <full-api-key>
Content-Type: application/json

{ "payload": "data" }

Or the v2 endpoint:

POST /inbound/v2/:key_prefix/:event_type
X-Satellite-Key: <full-api-key>

And the v3 contact-sync endpoint — POST /inbound/v3/:key_prefix/contact-sync (also survey-complete and contact-upsert) — with the same header.

Supported event types from satellite apps:

Outgoing Webhook Endpoints (Sending Data)

You can register endpoints that CoreSwift will POST events to. CoreSwift delivers events to each endpoint that is active and subscribes to that event type. A workspace configures its own endpoints, signing secret and event subscriptions in the console under Settings → Webhooks: that screen lists each endpoint's name, URL, events, active state, last successful delivery and failure count, and can add, edit, pause, activate and delete them. Outbound webhooks are sold on Enterprise/Agency — a workspace whose plan lacks the webhooks module has its requests to the whole surface refused with HTTP 402 and the reason in the response body. The platform console (admin.coreswiftcrm.com) has no editor: the endpoints are workspace-scoped, so it only points here. These same calls remain available directly on the API:

POST /api/integrations/webhooks
Authorization: Bearer ***

{
  "name": "Slack Notifier",
  "url": "https://hooks.slack.com/services/xxx",
  "secret": "your-signing-secret",
  "events": ["contact.created", "opportunity.won"],
  "retry_count": 3,
  "timeout_ms": 5000
}

List configured webhooks:

GET /api/integrations/webhooks
Authorization: Bearer ***

Response: { "webhooks": [...] }

What arrives. Each delivery is a JSON POST:

POST <your url>
X-CoreSwift-Event: contact.created
X-CoreSwift-Delivery: <endpoint id>
X-CoreSwift-Delivery-Attempt: 1
X-CoreSwift-Signature: t=1759512345,v1=<hex>

{
  "event": "contact.created",
  "tenant_id": "...",
  "webhook_id": "...",
  "delivered_at": "2026-10-06T16:45:00+00:00",
  "data": { ...the event payload... }
}

Verifying the signature. When the endpoint has a signing secret the X-CoreSwift-Signature header is t=<unix seconds>,v1=<hex>, where v1 is HMAC-SHA256(secret, "<t>.<raw request body>") — compute the same value and reject a mismatch. An endpoint saved without a secret is sent unsigned.

Which events, and retries. An endpoint whose events list is empty receives every event; a non-empty list receives only those event types. An endpoint with is_active: false receives nothing. A failed delivery (anything other than a 2xx) is retried retry_count times with a growing backoff, each attempt bounded by timeout_ms; redirects are never followed. The endpoint's last_triggered_at shows its last successful delivery and failure_count how many deliveries have failed since the last success.

Integration Targets

For portfolio-level integrations, CoreSwift supports Integration Targets named connections to external systems with webhook URLs and API keys:

POST /api/portfolio/:id/targets
Authorization: Bearer <token>

{
  "name": "Mailchimp Sync",
  "provider": "mailchimp",
  "webhook_url": "https://mailchimp.com/webhook",
  "portfolio_company_id": "optional-uuid"
}

Testing a Webhook

Use the simple test endpoint to verify connectivity:

POST /simple-hook
Content-Type: application/json

{ "test": true }
Response: { "ok": true }

Account Settings

Under Settings > Profile you can view and update your profile:

• Name Your display name
• Email Login email — you can move it to another address yourself: Profile → Sign-in email → enter the new address, and we email a confirmation link to it. Nothing changes until you open that link (the link works once and expires in 2 hours)
• Role admin (full access) or member (limited)

View your account:

GET /api/auth/me
Authorization: Bearer <token>

Change Password

PUT /api/profile/password
Authorization: Bearer <token>

{ "current_password": "<your-current-password>", "new_password": "NewSecurePass123!" }

Organization Settings

Your organization has its own profile:

• Name Your company/org name
• Slug URL-friendly identifier

GET /api/account/:id — View details
PATCH /api/account/:id — Update name

API Keys

API keys allow satellite apps to authenticate when sending data to CoreSwift via webhooks. Each key has:

• Key Prefix The leading characters of the key, carried in the webhook URL to select the row. It is public and is not a secret.
• Full Key The credential, sent in the X-Satellite-Key header. The server stores only its SHA-256 digest (key_hash), compares the two in constant time, and can never recover the full key from the row.
• Source App Which app this key is for (funnelswift, incentiveswift, etc.)
• Status Active or Disabled (a disabled key authenticates nothing)
• Last Used Timestamp of most recent usage

Satellite keys have no console screen: they are provisioned per tenant by the operator, who stores the prefix and the SHA-256 digest of the full key in the satellite_api_keys table (key_prefix, key_hash, source app, active flag, last used). The keys a workspace mints itself are the Lead-delivery keys (csk_…) in Settings > Integration Center, backed by POST /api/personal-api-keys (list, rotate and revoke alongside).

Portal & Portfolio Companies

For agency-level accounts, CoreSwift supports:

• Portfolio Companies Track multi-tenant clients under your agency (GET/POST /api/portfolio)
• Cross-App Sync Push data between apps: POST /api/admin/portfolio-sync
• Impersonation Admin can impersonate a user: POST /api/admin/impersonate

One built-in look

There is no preset-theme picker and no Appearance screen in the console today — the workspace ships a single built-in look. (A widget's own form carries an accent colour for that widget.)

Not in the console today

There is no reminder control on a deal, no reminder panel on the dashboard and no Overdue count, and no route that lists or creates reminders — so there is nothing to set up here yet.

Not in the console today

There is no Forecast screen and no forecast endpoint, so no weighted-pipeline view is shown anywhere. Deal value by stage is visible on Sales > Pipelines & Deals, which lists each pipeline's deals with its won / open / lost counts.

What is recorded

Every stage move is written down as it happens — which stage it moved from and to, and who moved it — so a deal's progression is kept.

What the app shows

The CRM has no Activity Timeline screen, and no endpoint that lists a deal's history, so that history is not visible in the app today. Platform-wide events (type, description, related entity, date) can be read through the API:

GET /api/events

Import Contacts from CSV

Migrate your existing contacts from any CRM or spreadsheet with a single CSV import:

1. Go to Contacts and click ⬆ Import CSV.
2. Upload your CSV via drag-and-drop or file browser.
3. Preview — CoreSwift reads the header row and shows you a preview of how fields will be mapped.
4. Batch Import — Click Import and the system creates contacts in bulk (up to 500 per batch).

Export to CSV

Two tables export to CSV: your contacts and your deals.

• From Contacts — Click ⬇ Export CSV on the Contacts screen to download all contacts as CSV
• From Pipelines & Deals — Click ⬇ Export deals to download every deal in the workspace as CSV, with its contact, company, pipeline and stage names

Import Deals from CSV

The same header row the export writes can be loaded straight back in, so an export doubles as a backup you can restore:

1. Go to Pipelines & Deals and click ⬆ Import deals.
2. Choose your file — the console shows every column it recognised and a few sample rows before anything is written.
3. Click Import deals — the board refreshes with the new cards, and the toast reports how many landed and how many were skipped.

Each row needs a name. pipeline and stage are used when the file names ones that exist; otherwise the row goes into your first pipeline. A contact is linked only when its email or full name matches an existing contact. A file with no name column is refused by the console instead of importing nothing.

Auto-Create Contact from Deal

The New Deal dialog links the deal to one of your existing contacts from a dropdown; it has no inline name/email/phone fields, so create the contact first if it is missing.

This pattern is also available in sister apps (FunnelSwift and IncentiveSwift) for seamless lead-to-deal creation.

Supported CSV Columns