Book a demo
To see exactly how we can help you drive your company in the right direction, book a demo with an expert.
Book a demo
CRM & Sales
CMap + Capsule CRM
Your pipeline and your projects, always in step.
Companies, contacts and opportunities sync both ways, no manual re-keying.
Available on the AEC and Consulting (PSA) editions.
Clients, contacts & projects
One source of truth
Companies & organisations
Contacts
Opportunities & projects
CRM & sales pipeline
In sync both ways
What syncs
Companies, contacts and opportunities, both directions
How it runs
Zapier, 13 published templates, no middleware
Works with
Capsule CRM
Included in
AEC and Consulting (PSA) editions
What the integrations does
One CRM. One project system. In sync.
Everything your sales and delivery teams key twice today moves automatically between CMap and Capsule CRM: companies, contacts and opportunities, in both directions, across 13 ready-made Zap templates.
CMap
→
Capsule
CMap
↔
Capsule
Capsule
→
CMap
Companies & organisations
New organisations in Capsule create companies in CMap, new CMap companies create Capsule organisations, and address or contact detail changes on either side keep both in step.
CMap
↔
Capsule
Capsule
→
CMap
CMap
→
Capsule
Contacts
People flow both ways and stay attached to the right company or organisation. New contacts are created on the other side, and job titles, emails and phone numbers stay current in both systems.
CMap
↔
Capsule
Capsule
→
CMap
CMap
→
Capsule
Opportunities & projects
Won opportunities in Capsule become CMap projects, and new CMap pipeline raises opportunities back in Capsule. Value, stage and close date changes flow both ways.
Why it matters
No double keying. No stale records.
CMap runs your projects; Capsule CRM runs your pipeline. This integration keeps them in step, both ways, automatically.
One source of truth
Sales and delivery see the same clients, contacts and opportunities, because they sync both ways without anyone re-keying them.
Records stay linked, not just copied
Each Zap writes the counterpart record ID back to the other system, so updates always land on the right record even after a rename.
No middleware to run
The sync runs through Zapier using CMap's published templates, so there is no extra software for your team to host or maintain.
Take only the flows you need
Thirteen templates, switched on individually. Start with one direction, add the rest when you are ready.
getting set up
Up and running on Zapier.
Setup uses Zapier and CMap's published Zap templates. Three steps, then it just runs. Companies, contacts and opportunities sync both ways automatically, on the AEC and Consulting (PSA) editions.
Connect your accounts
Sign in to CMap and Capsule CRM in Zapier with your usual credentials.
Add the ID fields
Create the custom fields in both systems that hold the linked record IDs.
Import and switch on
Import the templates you need, map the remaining fields, then turn the Zaps on in order.
Frequently asked questions
How is the integration set up?
It runs on Zapier. Sign in to CMap and Capsule CRM in Zapier with your usual credentials, add the custom ID fields in both systems, import CMap's published Zap templates, map the few fields the editor cannot pre-fill, then switch the Zaps on in order. No middleware is required.
Does the pipeline sync differ between the editions?
Only for creating opportunities from CMap. The Consulting (PSA) edition uses a New Potential trigger in CMap, while the AEC edition uses a New Project trigger. Every other workflow is the same on both editions.
Which CMap editions is this available on?
Both. The integration is available on the AEC edition and the Consulting (PSA) edition. The company, contact and update workflows are identical across both.
Capsule does not have separate companies and people. How does that work?
In Capsule everything is a Contact, with a Type of person or organisation. The Zap templates that deal with companies include a filter step so only organisation records are processed, and the contact templates only process person records.
How are records matched between the two systems?
By stored record ID. When a Zap creates a record it writes the new record's ID back to a custom field on its counterpart, and the update Zaps then match on that ID. Matching on ID rather than name means a rename or a change of email address does not break the link.
What data syncs between CMap and Capsule CRM?
Companies and organisations, contacts, and opportunities and projects, all in both directions. There are 13 published Zap templates in total, covering record creation and ongoing updates on both sides.
Does CMap integrate with Capsule CRM?
Yes. CMap connects to Capsule CRM through Zapier, using CMap's published Zap templates. Companies, contacts and opportunities sync both ways, with no middleware to host.
integrations
CMap, embedded in your wider tech stack
Capsule CRM is one of CMap's CRM integrations, available on the AEC and Consulting (PSA) editions, alongside the accounting, CRM and collaboration tools your business already runs on.
View all integrations
