›
›
›
›
HubSpot to Pipedrive migration checklist 2026
HubSpot to Pipedrive migration checklist 2026
HubSpot to Pipedrive migration checklist 2026
HubSpot to Pipedrive migration checklist 2026
HubSpot to Pipedrive migration checklist 2026
HubSpot to Pipedrive migration checklist 2026
Author
Aljaz Peklaj
Most teams that move from HubSpot to Pipedrive do it for one reason: they are paying enterprise-suite money for a sales team that needs a pipeline. Done in the right order, the migration is a one-to-two-week project with zero lost deals; done ad hoc, it is a quarter of duplicate contacts and orphaned activities. This checklist covers the data mapping, the step-by-step sequence, the three migration paths, and what you gain and lose on the other side.
The pricing math behind the switch lives in our HubSpot pricing and Pipedrive pricing breakdowns; the head-to-head is in Pipedrive vs HubSpot.
TL;DR
Migrate in this order: clean and dedupe in HubSpot first, export CSVs, build your custom fields and pipelines in Pipedrive, then import Organizations, Persons, Deals, Leads, Activities, and Notes, in that sequence, linking records on email as the unique key. The DIY CSV path is free and fits most databases; Import2 handles full-history automated migration when you need emails and attachments moved; Zapier or Make keeps both CRMs in sync during a parallel-run cutover. On cost, Pipedrive runs $14-99 per seat annually versus HubSpot's per-hub, per-tier stack, so a 10-seat sales team typically cuts CRM spend by half or more. Budget one week of prep, one day of import, and one week of parallel-run verification.
Map the data before you move it
HubSpot and Pipedrive name and structure objects differently, and every migration failure we see traces back to skipping this mapping step. Pipedrive's official migration guide confirms the core translations.
Contacts become Persons. Straight translation, but HubSpot's marketing/non-marketing contact split does not exist in Pipedrive: every imported person is just a person, so export the distinction as a custom field if your email tool needs it.
Companies become Organizations. Straight translation. Import these first so persons and deals have something to attach to.
Deals stay Deals. Pipelines and stages must exist in Pipedrive before import, and stage names should match your HubSpot pipeline one-to-one for the first quarter, so reporting stays comparable.
Tasks, calls, and emails become Activities. Pipedrive consolidates them under one entity with types. Logged email bodies do not travel via CSV: they need the automated path or stay archived in HubSpot.
Notes stay Notes, tickets have no home. Pipedrive has no service desk object. If you use Service Hub tickets, they stay behind or move to a dedicated support tool.
The 10-step checklist
Work the phases in order: prep, build, move, verify. The import order inside the move phase is the part teams get wrong most often.
1. Audit what you actually use. List active properties, pipelines, automations, and integrations in HubSpot. Most accounts carry years of unused fields; migrate the ones with data your team reads, not all of them.
2. Dedupe and clean in HubSpot. Merge duplicate contacts and companies before export, per HubSpot's export documentation. Garbage exported is garbage imported, now with new record IDs.
3. Export CSVs. Contacts, companies, deals with pipeline and stage, activities, and notes. Include the email column everywhere: it is the join key.
4. Build pipelines and stages in Pipedrive. Mirror your HubSpot stages exactly for the first quarter.
5. Create custom fields before import. Every HubSpot property you kept needs a matching Pipedrive custom field with the right type. Creating fields during import mapping is possible and messy.
6. Import in sequence. Organizations first, then Persons, then Deals, then Leads, then Activities, then Notes, mapping fields at each step and linking on email. Pipedrive's import wizard flags unmapped columns; resolve every one before confirming.
7. Spot-check 25 records per object. Open real records and verify owners, stages, amounts, close dates, and person-organization links survived.
8. Rebuild the automations that earn their keep. Pipedrive's workflow automation covers sequences, stage-triggered tasks, and field updates on the Advanced plan and up. Rebuild the five automations your team actually relies on, not the forty HubSpot accumulated.
9. Reconnect the integration stack. Email sync, calendar, enrichment, and your outreach tools all re-authenticate against Pipedrive. Do this before go-live, not after, so activity logging never gaps.
10. Parallel-run for one week, then cut off HubSpot edit access. Keep HubSpot read-only through the downgrade notice period as an archive, and set a calendar reminder for the renewal date so the old contract does not auto-renew.
Three migration paths and when each wins
Path 1: DIY CSV (free). The sequence above, using Pipedrive's native import tool, documented in Pipedrive's CRM data migration guide. Right for databases up to roughly 50k records where logged email history can stay archived in HubSpot. One to two weeks end to end.
Path 2: Automated full-history migration (paid). Import2 moves records with their complete history, including emails and attachments, with a sample migration to verify mapping before the full run. Quote-based pricing. Right when compliance or sales continuity requires the full record trail inside Pipedrive.
Path 3: Parallel-run sync (for staged cutovers). A Zapier or Make sync keeps new records flowing into both CRMs while teams switch in waves. Right for multi-team orgs that cannot cut over in one weekend. Retire the sync within a month; permanent two-CRM setups rot.
What you gain and what you lose
The gain is focus and price. Pipedrive's plans run $14-99 per seat per year on annual billing, the pipeline UX is faster for a pure sales motion, and reps log more because the tool asks less. Most 10-seat teams land on Advanced or Professional and cut CRM spend by half or more versus a Sales Hub Professional stack, before HubSpot's per-tier add-ons.
The loss is the suite. No marketing hub, no CMS, no native ticketing, thinner attribution reporting. If marketing runs email from HubSpot today, that motion needs a new home (our email list segmentation guide covers the dedicated-tool stack), and cross-object custom reporting is simply shallower in Pipedrive. Teams that use HubSpot as a true all-in-one should read the full comparison before committing; teams paying for the suite and using the pipeline should switch and stop reading.
FAQ
How long does a HubSpot to Pipedrive migration take?
One to two weeks for the standard path: several days of cleanup and field-building, a day for the actual CSV imports, and a week of parallel-run verification. Automated full-history migrations add a sample-run cycle up front but compress the import itself.
Can I migrate from HubSpot to Pipedrive for free?
Yes. HubSpot exports CSVs on every tier and Pipedrive's native import wizard handles contacts, companies, deals, activities, and notes without paid tools. You pay only when you need logged emails and attachments moved automatically, which is Import2's territory.
Does deal history transfer from HubSpot to Pipedrive?
Deal records, stages, amounts, owners, and dates transfer cleanly via CSV. Full engagement history, logged email bodies and attachments, does not travel in CSVs: use an automated migration service to bring it, or keep HubSpot read-only as the archive.
What is the correct import order in Pipedrive?
Organizations, then Persons, then Deals, then Leads, then Activities, then Notes. Parents before children, so every later import has records to link to, with email as the unique key throughout.
Is Pipedrive cheaper than HubSpot?
For a sales-led team, substantially: Pipedrive runs $14-99 per seat per year across five plans, while comparable HubSpot Sales Hub tiers price per seat at multiples of that before add-ons. The gap narrows if you would otherwise buy separate marketing and support tools to replace the suite.
What does Pipedrive not have that HubSpot has?
Marketing automation hub, CMS, native ticketing, marketing contacts, and deeper cross-object reporting. Pipedrive covers the sales pipeline, workflow automation, and email sync, and expects marketing and support to live in dedicated tools.
Bottom line
A HubSpot to Pipedrive migration is a data project wearing a procurement decision: map objects first, clean before export, build fields before import, import parents before children, and parallel-run before cutting over. The free CSV path covers most teams, Import2 covers full-history requirements, and the reward is a CRM bill cut in half and a pipeline your reps update without being chased.
Want the migration run for you, automations rebuilt and stack rewired included? Book a call with GROU. We run RevOps and CRM migrations inside B2B revenue engines across verticals.
We are GROU, a B2B pipeline agency that runs lead generation, outbound, and LinkedIn content for clients across manufacturing, fintech, iGaming, software, and professional services. The checklist reflects our CRM migration and RevOps deployments between 2024 and 2026, anonymized to protect client confidentiality.
Some links in this article are affiliate. We may earn a small commission at no extra cost to you. We only recommend tools we've deployed for clients.
Most teams that move from HubSpot to Pipedrive do it for one reason: they are paying enterprise-suite money for a sales team that needs a pipeline. Done in the right order, the migration is a one-to-two-week project with zero lost deals; done ad hoc, it is a quarter of duplicate contacts and orphaned activities. This checklist covers the data mapping, the step-by-step sequence, the three migration paths, and what you gain and lose on the other side.
The pricing math behind the switch lives in our HubSpot pricing and Pipedrive pricing breakdowns; the head-to-head is in Pipedrive vs HubSpot.
TL;DR
Migrate in this order: clean and dedupe in HubSpot first, export CSVs, build your custom fields and pipelines in Pipedrive, then import Organizations, Persons, Deals, Leads, Activities, and Notes, in that sequence, linking records on email as the unique key. The DIY CSV path is free and fits most databases; Import2 handles full-history automated migration when you need emails and attachments moved; Zapier or Make keeps both CRMs in sync during a parallel-run cutover. On cost, Pipedrive runs $14-99 per seat annually versus HubSpot's per-hub, per-tier stack, so a 10-seat sales team typically cuts CRM spend by half or more. Budget one week of prep, one day of import, and one week of parallel-run verification.
Map the data before you move it
HubSpot and Pipedrive name and structure objects differently, and every migration failure we see traces back to skipping this mapping step. Pipedrive's official migration guide confirms the core translations.
Contacts become Persons. Straight translation, but HubSpot's marketing/non-marketing contact split does not exist in Pipedrive: every imported person is just a person, so export the distinction as a custom field if your email tool needs it.
Companies become Organizations. Straight translation. Import these first so persons and deals have something to attach to.
Deals stay Deals. Pipelines and stages must exist in Pipedrive before import, and stage names should match your HubSpot pipeline one-to-one for the first quarter, so reporting stays comparable.
Tasks, calls, and emails become Activities. Pipedrive consolidates them under one entity with types. Logged email bodies do not travel via CSV: they need the automated path or stay archived in HubSpot.
Notes stay Notes, tickets have no home. Pipedrive has no service desk object. If you use Service Hub tickets, they stay behind or move to a dedicated support tool.
The 10-step checklist
Work the phases in order: prep, build, move, verify. The import order inside the move phase is the part teams get wrong most often.
1. Audit what you actually use. List active properties, pipelines, automations, and integrations in HubSpot. Most accounts carry years of unused fields; migrate the ones with data your team reads, not all of them.
2. Dedupe and clean in HubSpot. Merge duplicate contacts and companies before export, per HubSpot's export documentation. Garbage exported is garbage imported, now with new record IDs.
3. Export CSVs. Contacts, companies, deals with pipeline and stage, activities, and notes. Include the email column everywhere: it is the join key.
4. Build pipelines and stages in Pipedrive. Mirror your HubSpot stages exactly for the first quarter.
5. Create custom fields before import. Every HubSpot property you kept needs a matching Pipedrive custom field with the right type. Creating fields during import mapping is possible and messy.
6. Import in sequence. Organizations first, then Persons, then Deals, then Leads, then Activities, then Notes, mapping fields at each step and linking on email. Pipedrive's import wizard flags unmapped columns; resolve every one before confirming.
7. Spot-check 25 records per object. Open real records and verify owners, stages, amounts, close dates, and person-organization links survived.
8. Rebuild the automations that earn their keep. Pipedrive's workflow automation covers sequences, stage-triggered tasks, and field updates on the Advanced plan and up. Rebuild the five automations your team actually relies on, not the forty HubSpot accumulated.
9. Reconnect the integration stack. Email sync, calendar, enrichment, and your outreach tools all re-authenticate against Pipedrive. Do this before go-live, not after, so activity logging never gaps.
10. Parallel-run for one week, then cut off HubSpot edit access. Keep HubSpot read-only through the downgrade notice period as an archive, and set a calendar reminder for the renewal date so the old contract does not auto-renew.
Three migration paths and when each wins
Path 1: DIY CSV (free). The sequence above, using Pipedrive's native import tool, documented in Pipedrive's CRM data migration guide. Right for databases up to roughly 50k records where logged email history can stay archived in HubSpot. One to two weeks end to end.
Path 2: Automated full-history migration (paid). Import2 moves records with their complete history, including emails and attachments, with a sample migration to verify mapping before the full run. Quote-based pricing. Right when compliance or sales continuity requires the full record trail inside Pipedrive.
Path 3: Parallel-run sync (for staged cutovers). A Zapier or Make sync keeps new records flowing into both CRMs while teams switch in waves. Right for multi-team orgs that cannot cut over in one weekend. Retire the sync within a month; permanent two-CRM setups rot.
What you gain and what you lose
The gain is focus and price. Pipedrive's plans run $14-99 per seat per year on annual billing, the pipeline UX is faster for a pure sales motion, and reps log more because the tool asks less. Most 10-seat teams land on Advanced or Professional and cut CRM spend by half or more versus a Sales Hub Professional stack, before HubSpot's per-tier add-ons.
The loss is the suite. No marketing hub, no CMS, no native ticketing, thinner attribution reporting. If marketing runs email from HubSpot today, that motion needs a new home (our email list segmentation guide covers the dedicated-tool stack), and cross-object custom reporting is simply shallower in Pipedrive. Teams that use HubSpot as a true all-in-one should read the full comparison before committing; teams paying for the suite and using the pipeline should switch and stop reading.
FAQ
How long does a HubSpot to Pipedrive migration take?
One to two weeks for the standard path: several days of cleanup and field-building, a day for the actual CSV imports, and a week of parallel-run verification. Automated full-history migrations add a sample-run cycle up front but compress the import itself.
Can I migrate from HubSpot to Pipedrive for free?
Yes. HubSpot exports CSVs on every tier and Pipedrive's native import wizard handles contacts, companies, deals, activities, and notes without paid tools. You pay only when you need logged emails and attachments moved automatically, which is Import2's territory.
Does deal history transfer from HubSpot to Pipedrive?
Deal records, stages, amounts, owners, and dates transfer cleanly via CSV. Full engagement history, logged email bodies and attachments, does not travel in CSVs: use an automated migration service to bring it, or keep HubSpot read-only as the archive.
What is the correct import order in Pipedrive?
Organizations, then Persons, then Deals, then Leads, then Activities, then Notes. Parents before children, so every later import has records to link to, with email as the unique key throughout.
Is Pipedrive cheaper than HubSpot?
For a sales-led team, substantially: Pipedrive runs $14-99 per seat per year across five plans, while comparable HubSpot Sales Hub tiers price per seat at multiples of that before add-ons. The gap narrows if you would otherwise buy separate marketing and support tools to replace the suite.
What does Pipedrive not have that HubSpot has?
Marketing automation hub, CMS, native ticketing, marketing contacts, and deeper cross-object reporting. Pipedrive covers the sales pipeline, workflow automation, and email sync, and expects marketing and support to live in dedicated tools.
Bottom line
A HubSpot to Pipedrive migration is a data project wearing a procurement decision: map objects first, clean before export, build fields before import, import parents before children, and parallel-run before cutting over. The free CSV path covers most teams, Import2 covers full-history requirements, and the reward is a CRM bill cut in half and a pipeline your reps update without being chased.
Want the migration run for you, automations rebuilt and stack rewired included? Book a call with GROU. We run RevOps and CRM migrations inside B2B revenue engines across verticals.
We are GROU, a B2B pipeline agency that runs lead generation, outbound, and LinkedIn content for clients across manufacturing, fintech, iGaming, software, and professional services. The checklist reflects our CRM migration and RevOps deployments between 2024 and 2026, anonymized to protect client confidentiality.
Some links in this article are affiliate. We may earn a small commission at no extra cost to you. We only recommend tools we've deployed for clients.
Most teams that move from HubSpot to Pipedrive do it for one reason: they are paying enterprise-suite money for a sales team that needs a pipeline. Done in the right order, the migration is a one-to-two-week project with zero lost deals; done ad hoc, it is a quarter of duplicate contacts and orphaned activities. This checklist covers the data mapping, the step-by-step sequence, the three migration paths, and what you gain and lose on the other side.
The pricing math behind the switch lives in our HubSpot pricing and Pipedrive pricing breakdowns; the head-to-head is in Pipedrive vs HubSpot.
TL;DR
Migrate in this order: clean and dedupe in HubSpot first, export CSVs, build your custom fields and pipelines in Pipedrive, then import Organizations, Persons, Deals, Leads, Activities, and Notes, in that sequence, linking records on email as the unique key. The DIY CSV path is free and fits most databases; Import2 handles full-history automated migration when you need emails and attachments moved; Zapier or Make keeps both CRMs in sync during a parallel-run cutover. On cost, Pipedrive runs $14-99 per seat annually versus HubSpot's per-hub, per-tier stack, so a 10-seat sales team typically cuts CRM spend by half or more. Budget one week of prep, one day of import, and one week of parallel-run verification.
Map the data before you move it
HubSpot and Pipedrive name and structure objects differently, and every migration failure we see traces back to skipping this mapping step. Pipedrive's official migration guide confirms the core translations.
Contacts become Persons. Straight translation, but HubSpot's marketing/non-marketing contact split does not exist in Pipedrive: every imported person is just a person, so export the distinction as a custom field if your email tool needs it.
Companies become Organizations. Straight translation. Import these first so persons and deals have something to attach to.
Deals stay Deals. Pipelines and stages must exist in Pipedrive before import, and stage names should match your HubSpot pipeline one-to-one for the first quarter, so reporting stays comparable.
Tasks, calls, and emails become Activities. Pipedrive consolidates them under one entity with types. Logged email bodies do not travel via CSV: they need the automated path or stay archived in HubSpot.
Notes stay Notes, tickets have no home. Pipedrive has no service desk object. If you use Service Hub tickets, they stay behind or move to a dedicated support tool.
The 10-step checklist
Work the phases in order: prep, build, move, verify. The import order inside the move phase is the part teams get wrong most often.
1. Audit what you actually use. List active properties, pipelines, automations, and integrations in HubSpot. Most accounts carry years of unused fields; migrate the ones with data your team reads, not all of them.
2. Dedupe and clean in HubSpot. Merge duplicate contacts and companies before export, per HubSpot's export documentation. Garbage exported is garbage imported, now with new record IDs.
3. Export CSVs. Contacts, companies, deals with pipeline and stage, activities, and notes. Include the email column everywhere: it is the join key.
4. Build pipelines and stages in Pipedrive. Mirror your HubSpot stages exactly for the first quarter.
5. Create custom fields before import. Every HubSpot property you kept needs a matching Pipedrive custom field with the right type. Creating fields during import mapping is possible and messy.
6. Import in sequence. Organizations first, then Persons, then Deals, then Leads, then Activities, then Notes, mapping fields at each step and linking on email. Pipedrive's import wizard flags unmapped columns; resolve every one before confirming.
7. Spot-check 25 records per object. Open real records and verify owners, stages, amounts, close dates, and person-organization links survived.
8. Rebuild the automations that earn their keep. Pipedrive's workflow automation covers sequences, stage-triggered tasks, and field updates on the Advanced plan and up. Rebuild the five automations your team actually relies on, not the forty HubSpot accumulated.
9. Reconnect the integration stack. Email sync, calendar, enrichment, and your outreach tools all re-authenticate against Pipedrive. Do this before go-live, not after, so activity logging never gaps.
10. Parallel-run for one week, then cut off HubSpot edit access. Keep HubSpot read-only through the downgrade notice period as an archive, and set a calendar reminder for the renewal date so the old contract does not auto-renew.
Three migration paths and when each wins
Path 1: DIY CSV (free). The sequence above, using Pipedrive's native import tool, documented in Pipedrive's CRM data migration guide. Right for databases up to roughly 50k records where logged email history can stay archived in HubSpot. One to two weeks end to end.
Path 2: Automated full-history migration (paid). Import2 moves records with their complete history, including emails and attachments, with a sample migration to verify mapping before the full run. Quote-based pricing. Right when compliance or sales continuity requires the full record trail inside Pipedrive.
Path 3: Parallel-run sync (for staged cutovers). A Zapier or Make sync keeps new records flowing into both CRMs while teams switch in waves. Right for multi-team orgs that cannot cut over in one weekend. Retire the sync within a month; permanent two-CRM setups rot.
What you gain and what you lose
The gain is focus and price. Pipedrive's plans run $14-99 per seat per year on annual billing, the pipeline UX is faster for a pure sales motion, and reps log more because the tool asks less. Most 10-seat teams land on Advanced or Professional and cut CRM spend by half or more versus a Sales Hub Professional stack, before HubSpot's per-tier add-ons.
The loss is the suite. No marketing hub, no CMS, no native ticketing, thinner attribution reporting. If marketing runs email from HubSpot today, that motion needs a new home (our email list segmentation guide covers the dedicated-tool stack), and cross-object custom reporting is simply shallower in Pipedrive. Teams that use HubSpot as a true all-in-one should read the full comparison before committing; teams paying for the suite and using the pipeline should switch and stop reading.
FAQ
How long does a HubSpot to Pipedrive migration take?
One to two weeks for the standard path: several days of cleanup and field-building, a day for the actual CSV imports, and a week of parallel-run verification. Automated full-history migrations add a sample-run cycle up front but compress the import itself.
Can I migrate from HubSpot to Pipedrive for free?
Yes. HubSpot exports CSVs on every tier and Pipedrive's native import wizard handles contacts, companies, deals, activities, and notes without paid tools. You pay only when you need logged emails and attachments moved automatically, which is Import2's territory.
Does deal history transfer from HubSpot to Pipedrive?
Deal records, stages, amounts, owners, and dates transfer cleanly via CSV. Full engagement history, logged email bodies and attachments, does not travel in CSVs: use an automated migration service to bring it, or keep HubSpot read-only as the archive.
What is the correct import order in Pipedrive?
Organizations, then Persons, then Deals, then Leads, then Activities, then Notes. Parents before children, so every later import has records to link to, with email as the unique key throughout.
Is Pipedrive cheaper than HubSpot?
For a sales-led team, substantially: Pipedrive runs $14-99 per seat per year across five plans, while comparable HubSpot Sales Hub tiers price per seat at multiples of that before add-ons. The gap narrows if you would otherwise buy separate marketing and support tools to replace the suite.
What does Pipedrive not have that HubSpot has?
Marketing automation hub, CMS, native ticketing, marketing contacts, and deeper cross-object reporting. Pipedrive covers the sales pipeline, workflow automation, and email sync, and expects marketing and support to live in dedicated tools.
Bottom line
A HubSpot to Pipedrive migration is a data project wearing a procurement decision: map objects first, clean before export, build fields before import, import parents before children, and parallel-run before cutting over. The free CSV path covers most teams, Import2 covers full-history requirements, and the reward is a CRM bill cut in half and a pipeline your reps update without being chased.
Want the migration run for you, automations rebuilt and stack rewired included? Book a call with GROU. We run RevOps and CRM migrations inside B2B revenue engines across verticals.
We are GROU, a B2B pipeline agency that runs lead generation, outbound, and LinkedIn content for clients across manufacturing, fintech, iGaming, software, and professional services. The checklist reflects our CRM migration and RevOps deployments between 2024 and 2026, anonymized to protect client confidentiality.
Some links in this article are affiliate. We may earn a small commission at no extra cost to you. We only recommend tools we've deployed for clients.
Pipeline OS Newsletter
Build qualified pipeline
Get weekly tactics to generate demand, improve lead quality, and book more meetings.
Trusted by industry leaders
Trusted by industry leaders
Trusted by industry leaders
Ready to build qualified pipeline?
Ready to build qualified pipeline?
Ready to build qualified pipeline?
Book a call to see if we're the right fit, or take the 2-minute quiz to get a clear starting point.
Book a call to see if we're the right fit, or take the 2-minute quiz to get a clear starting point.
Book a call to see if we're the right fit, or take the 2-minute quiz to get a clear starting point.
![](data:image/svg+xml,<svg display="block" role="presentation" viewBox="0 0 30 30" xmlns="http://www.w3.org/2000/svg"><path d="M 15.108 0 C 6.764 0 0 6.764 0 15.108 C 0 23.452 6.764 30.216 15.108 30.216 C 23.452 30.216 30.216 23.452 30.216 15.108 C 30.216 6.764 23.452 0 15.108 0 Z M 11.41 21.37 L 8.35 21.37 L 8.35 11.525 L 11.41 11.525 Z M 9.861 10.316 C 8.895 10.316 8.27 9.631 8.27 8.785 C 8.27 7.921 8.914 7.257 9.901 7.257 C 10.887 7.257 11.492 7.921 11.511 8.785 C 11.511 9.631 10.887 10.316 9.861 10.316 Z M 22.584 21.37 L 19.524 21.37 L 19.524 15.914 C 19.524 14.644 19.08 13.782 17.974 13.782 C 17.129 13.782 16.627 14.365 16.405 14.927 C 16.323 15.127 16.303 15.41 16.303 15.692 L 16.303 21.369 L 13.242 21.369 L 13.242 14.664 C 13.242 13.435 13.202 12.408 13.161 11.523 L 15.82 11.523 L 15.96 12.891 L 16.021 12.891 C 16.424 12.249 17.411 11.301 19.062 11.301 C 21.074 11.301 22.584 12.65 22.584 15.549 Z" fill="rgb(0, 0, 0)" height="30.21639343089746px" id="hfGbXmQR2" width="30.216393430897455px"/></svg>)
Copyright © 2026 – All Right Reserved
Company
Resources
Copyright © 2026 – All Right Reserved
Copyright © 2026 – All Right Reserved