Your companies, contacts, projects, quotations, and action history all transfer across using pre-configured import templates. Every import is scoped and configured by the ConstructionCRM team as part of your onboarding, and subsequent imports can be run by your own administrators once templates are in place.
The Data Import Tool ships with sample templates for every core entity type: Company, Contact, Project, and Links. The vendor configures templates to match your existing data format as part of onboarding, so you can run further imports yourself without assistance.
You provide your existing data as CSV or Excel. The import template is configured to match your field names and structure before anything is touched.
Templates are configured in the Data Import Tool for each entity: companies, contacts, projects, and relationship link assignments between them.
The import validates records before committing. Duplicate matching, broken links, and missing required fields are surfaced for review first.
Records load into the system with full relational links intact. Companies, contacts, and projects are linked automatically via the role assignment import.
Once templates are configured, you can run further imports independently. Useful for ongoing Sage syncs, new subcontractor lists, or acquired data sets.
Horizontal CRM platforms require extensive customisation to serve construction businesses. The same four problems appear every time, and they cannot be solved by configuration alone.
Generic CRMs have no concept of a Project with site details, storeys, units, or a supply chain of eleven companies each playing a distinct role. These require costly custom object development.
Lead data from the UK's major project intelligence providers has to be imported manually or via third-party connectors. ConstructionCRM ingests both natively with full field mapping and category code translation.
Construction Line registration, insurance reference, and insurance renewal date are not fields any general-purpose CRM ships with. In CCRM they are native to the Sub Contractor company type.
A lead-to-close pipeline does not reflect how a construction project progresses. CCRM uses a lettered stage system from Heads Up through PQQ Submission to Tender Submitted, In Production, and Won.
No add-on projects. No integration fees. The full CCRM feature set is available as soon as your companies, contacts, projects, and opportunities are in the system.
Tender, quote, and opportunity records linked directly to project records, with a lettered pipeline stage system that sorts correctly and reflects how procurement actually progresses on a construction project.
The Outlook Suite covers calendar sync, email auto-logging, and the Mailbox Listener, which captures any outbound email via BCC from any email client and logs it against the correct company record.
Formal proposals with version-suffixed proposal numbers, a multi-step approval workflow, quote issuance via branded templates, and line-item margin visibility updated in real time as you build the quote.
Built-in dashboards covering pipeline, geography, tender workload, and forecast by business unit, plus a native Power BI tab for advanced analytics, available without leaving the CRM application.
Aletus AI is a construction-specific intelligence platform integrated directly into ConstructionCRM. It is currently transitioning to a Claude (Anthropic) integration across three phases, bringing natural language querying to your live CRM data. No SQL. No BI analysts. No separate tool.
All bespoke work — whether a new field, a custom workflow, a report template, or an entirely new module — is governed by a Change Request Document (CRD). Nothing goes into development until the scope is written down, estimated, and signed off by both parties.
Each CRD includes a numbered development task list, deployment prerequisites the client must provide, a full list of deliverables, chargeability and estimated development time, and a formal sign-off block. The CRD supersedes all prior conversations and becomes the master document for delivery. Up to five revisions are included in the scoping process.
Every CRD passes through five stages before close: Scoping, where tasks and estimates are agreed; Waiting, for client prerequisites; In Development, where work is built and tested; Internal Demo, where the team reviews before client access; and Client Sign Off, where the deliverable is confirmed and the CRD is closed.
The range is wide. A CRD can cover field renames and new dropdown options in the Field Manager, mandatory field validation with visual enforcement, automated email alerts triggered by project dates, custom quote template layouts, entirely new modules built on the Generic Entity engine, and ERP integrations with full field mapping.
The construction data model was the deciding factor. Every company linked to a project with its own role, native Barbour ABI import, and pipeline stages that actually reflect how tendering works. We were not starting from a blank Salesforce org and billing a consultant to rebuild it.
CCRM is priced on a per-seat basis with contract terms managed per account. Bespoke customisation is scoped separately through the CRD process at a published rate, so you always know what a piece of work will cost before it starts.
Seat counts, contract start and renewal dates, and invoicing frequency are all managed per account. Monthly or annual billing available.
Bespoke development is invoiced at 70% upfront and 30% on deployment. Where a client deploys themselves, the 30% balance is due on handover. Out-of-hours work is charged at a premium rate.
Where a support bundle is in place, CRD hours are deducted from the bundle rather than invoiced separately. Deployment into the client environment (typically up to 45 minutes) is also drawn from the support bundle unless otherwise stated.
Book a 30-minute call. We will review your current system, scope the import templates, and tell you honestly how the migration would work for your data.