Skip to main content
Connect your CRM so companies and deals stay in sync between systems. Metal supports DealCloud, Salesforce, Affinity, and Dynamo. Inbound sync is available for those CRMs. Writing Metal edits back to the CRM is a separate, organization-level capability for DealCloud and Salesforce only. See Write edits back to your CRM.

​
Enable a CRM (admin)

1

Open Integrations

Go to Settings → Integrations and find your CRM.
2

Enable and authorize

Click into the CRM and follow its setup. Some CRMs need credentials — for example, DealCloud asks for a Client ID, API Key, and Base Url before you click Connect.

​
Connect your account (user)

Where a CRM supports per-user sign-in, connect your account at Settings → Connections once an admin has enabled it. Salesforce is a firm-level integration. After Salesforce is enabled, org admins can connect it from Settings → Connections → Salesforce. Users who already connected Salesforce also see it there so they can manage or disconnect their connection.
Setting up a CRM is part of onboarding — the Setup checklist includes an Integrate CRM step. See Onboarding your workspace.

​
Investor Relations records from DealCloud

When your DealCloud connection includes the corresponding object mappings, Metal can also sync these records into Investor Relations:
  • Funds
  • Limited Partners
  • Fundraising Processes
The records use the field mappings, filters, and incremental import configured for your DealCloud connection. Incoming fundraising status and stage values map to the fundraising taxonomy in your Metal organization. If these records do not appear after DealCloud is connected, the IR object mappings may not be configured. Contact support@metal.ai for help.

​
Write edits back to your CRM

CRM writeback sends a change you make in Metal to the matching field in DealCloud or Salesforce. Metal saves the edit first. The CRM update is asynchronous and does not block the Metal save. Writeback is opt-in. Metal enables it for your organization; it is not on by default. Affinity and Dynamo sync into Metal. They do not receive writeback.
If mapped CRM fields are read-only, or you do not see a sync badge after an edit, writeback is not enabled or the field has no working write path. Ask your Metal admin or contact support@metal.ai.

​
When an edit writes back

All of these must be true:
  • Writeback is enabled for your organization.
  • The record already exists in DealCloud or Salesforce and is linked in Metal.
  • You edited the field in Metal (for example on the record page or in a list).
  • The field is mapped in your CRM configuration.
Unmapped fields stay editable in Metal only. A registered field with no mapping is skipped; other fields in the same edit can still write. Metal-native records — created only in Metal, with no CRM link — have nothing to write back to.

​
What you can change

On a CRM-linked record, Metal labels who owns each field: Deal financials imported from the CRM (for example revenue or EBITDA) stay read-only. There is no writeback path for those fields today. The most complete writeback coverage is on deals. When the field is mapped, typical deal writes include status and stage, name, notes, size, priority, and dates. They also include target company, source company, source contact, owners, deal advisors, IOI / LOI / final bid dates and amounts, and mapped custom deal fields. Companies, people, and activities can also write mapped fields back when writeback is enabled. Coverage is narrower than deals and depends on your mappings. Investor Relations records that sync from DealCloud remain read-only for mapped fundraising fields until an outbound path is enabled for your organization.

​
After you save

After you save, each mapped field shows a sync badge — for example Syncing, Synced, Dry-run, Sync failed, or Action needed. Sync failed includes a Retry button after you fix the value or CRM error. A Dry-run badge means Metal validated the write without sending it; when your organization has turned off CRM dry-run, use Push to CRM on that lane to send it. Action needed marks a blocked lane: the badge shows the reason, with no Retry button, because the app does not yet offer a resolution form for blocked lanes. Clearing a CRM-linked field is not the same as leaving it blank. Empty values are not sent as clears. Clearing the company on a CRM-sourced deal is rejected. See Working with deals.

​
Deal intake and workflow writes

Teaser and CIM intake can create or update the CRM as a configured workflow step. That path is organization-specific. It is not the same as editing a field on a record in Metal and waiting for writeback. Do not assume every workflow write uses this in-app writeback path. Confirm the review step and CRM write behavior with your Metal admin before you treat an intake run as the system of record.