Standardisation pays off
When several business units share a platform, the same workflows make administration and training simpler.
CASE STUDY · STEEL & CONSTRUCTION · CRM
An industrial group in steel distribution and construction moved CRM, sales and project delivery for two businesses into one ClickUp workspace. Dtech migrated more than 100,000 records and wrote custom code to connect them and put customers on a map.
The client is not named. Workspace screens, records and maps on this page are recreated with sample data.
01Who they are
The client is an industrial group working in steel distribution and related construction and architectural services. Customer relationships, sales opportunities and project work ran across several businesses. Two of its business units took part in the project.
Both business units run on the same underlying structure, so the workspace can be managed as one.
02Where they started
Reporting, customer information, sales activity and project work sat in different systems that did not talk to each other. The group wanted one consistent way to run these operations across its businesses. Moving the data was only part of it: the information had to be useful for everyday work once it arrived.
| id | name 3 | town | postcode 1 | lat,lng |
|---|---|---|---|---|
| ACC-1042 | Hartley Steel Fabrication Ltd | Leeds | ls11 5px | empty |
| ACC-1043 | Northgate Cladding | Wakefield | WF1 2DQ | empty |
| ACC-1044 | Hartley Steel Fab. | Leeds | LS11 5PX | empty |
| ACC-1045 | Pennine Roofing Supplies | Halifax | hx1 1qe | empty |
| id | customer 2 | value |
|---|---|---|
| OPP-2291 | Hartley Steel Fab | £48,000 |
| OPP-2292 | northgate cladding ltd | £112,500 |
| OPP-2307 | Hartley Steel Fabrication | £23,900 |
1Postcodes stored as plain text, with no latitude or longitude for a map.
2Opportunities pointing to customers by typed name, not by record.
3The same customer entered more than once, spelled differently.
The kind of exports the migration started from, recreated with sample data.
Bring customer and sales information into one platform.
Create structured sales pipelines and project workflows.
See opportunities, ownership and progress clearly.
Connect customer records with related sales information.
Visualise customer locations across towns and counties.
Migrate the data without losing relationships between records.
03What we built
Instead of a different setup for each business, Dtech designed one ClickUp structure and used it for both. CRM lists hold customers, contacts, meetings and leads. A sales pipeline tracks opportunities. A project delivery structure follows work from incoming to completed or lost. Relationship fields tie it all together.
| Customer | Town | Opportunities | Contacts | Account owner |
|---|---|---|---|---|
| Hartley Steel Fabrication | Leeds | 2 | 3 | A. Patel |
| Northgate Cladding | Wakefield | 1 | 2 | J. Morris |
| Pennine Roofing Supplies | Halifax | 3 | 1 | A. Patel |
| Calder Valley Builders | Huddersfield | 1 | 4 | R. Shaw |
Each customer links to its opportunities, contacts and meetings, so related records open from one place.
Stage names are illustrative. Longer-running opportunities keep their value, decision date and owner on the card.
Schematic map with sample counts. Pins come from postcodes converted to coordinates during the migration.
Recreated with sample data. Switch tabs to see each view.
04How the data moved
Data migration became a large part of the engagement. Importing customers and opportunities as separate rows would have produced a list, not a connected CRM. The source records needed cleaning and restructuring first, and ClickUp’s Map view needs coordinates that the postcode text did not have.
Fix formats, spacing and duplicates in the source files.
Reshape rows to match ClickUp lists and custom fields.
Turn each postcode into latitude and longitude.
Connect each opportunity to its customer record.
Load into ClickUp through the API.
// Illustrative excerpt – simplified
for (const row of customers) {
const { lat, lng } = await geocode(normalise(row.postcode));
await clickup.updateTask(row.taskId, {
location: { lat, lng },
opportunities: links.get(row.accountId)
});
}A simplified, illustrative excerpt. Dtech’s scripts used the ClickUp API to process the data, add coordinates and link related records.
05What changed
Dtech completed the implementation and data migration for both participating business units. After go-live, a new ClickUp champion on the client side took responsibility for the workspace.
cleaned, linked and imported
on one shared structure
CRM, sales, delivery and mapping
for geocoding and record linking
Dtech did not have visibility into usage after handover, so long-term adoption and productivity gains could not be independently confirmed.
06Lessons learned
When several business units share a platform, the same workflows make administration and training simpler.
Source data has to be cleaned, structured and connected. When standard imports fall short, plan for development work.
A clear transition plan keeps continuity when a client-side champion takes over, and makes it easier to follow up on adoption.
Bringing several businesses together takes more than shared software. Dtech set up standard CRM, sales and project workflows for two business units, migrated more than 100,000 records, and built custom code to connect customer data and map it.
How an aviation organisation moved its IT and PMO departments off spreadsheets and into ClickUp.
BOOK THE FIRST HOUR
As a ClickUp Diamond Partner, we are measured on real adoption, not hours billed. If the first session works, your team will ask for more. If it does not, we stop there.
Book a Free Hour