Frequently asked questions

For up to 50,000 records, a Pipedrive to HubSpot migration typically takes two to three weeks covering discovery, field mapping, a sandbox dry run and live cutover. Larger datasets of 500,000 records or more usually run four to six weeks with a phased approach, because reconciliation and deduplication take longer than the load itself.

Yes. We migrate standard Salesforce objects (Accounts, Contacts, Opportunities, Cases) and custom objects, preserving relationships, field history and attachments through custom API scripts. The hard part is usually translating Salesforce record types and validation rules into a HubSpot model that stays simple, so that work happens during discovery rather than mid-load.

Yes. We build custom ETL pipelines to extract from SQL databases, Excel and CSV files, or legacy systems with REST and SOAP APIs, then clean and transform the data before loading it into HubSpot. Anything with a readable data store can be migrated; the effort scales with how inconsistent the source data is, not with how old the system is.

We run deduplication against multiple criteria — email, company domain and name similarity — before the load, then configure HubSpot's duplicate detection afterwards and hand over a resolution report. On large projects we deliberately separate migration and deduplication into two phases, because merging while loading makes it impossible to reconcile record counts.

Historical data migrates in the background while your team keeps working in the source CRM. Cutover uses a delta sync to pick up anything created or changed during the load, and needs a read-only window of under an hour, scheduled outside business hours. No records are lost during that window.

Yes. Attachments, meeting notes, call logs, email threads and task history all migrate with their original timestamps and associations to contacts, companies, deals and tickets. Attachments are usually the slowest object to move, so we start them early in the schedule rather than at the end.

Every custom field is mapped explicitly in a signed mapping document, and picklist values are enumerated exhaustively. Unmatched values are flagged for review rather than silently dropped — we either transform them to an existing option or create the new option in HubSpot, but never guess.

We run validation scripts before and after the load comparing record counts, field fill rates and association counts, then deliver a reconciliation report explaining every variance. Expected variances (excluded test records, agreed skips) are listed with the rule that produced them; anything unexplained is treated as a defect and worked until it is zero.

Yes. We handle flat files with custom header mapping, data type validation and relationship inference for parent-child rows, cleaning malformed data before import. Spreadsheet migrations usually take longer per record than CRM-to-CRM migrations because the source has no schema to rely on.

Yes. We consolidate multiple CRMs, spreadsheets and databases into a single portal with explicit conflict resolution rules — which source wins per field, how records are matched, and what happens to conflicting owners. Those rules are agreed in writing before any data moves.

You choose during discovery: exclude soft-deleted records entirely, import them marked inactive, or preserve them with a status flag for audit purposes. Whichever option you pick is documented in the mapping so the reconciliation report accounts for the difference in counts.

Every migration includes 30 days of hypercare: daily monitoring, data reconciliation checks, user question handling and fixes for anything the first weeks of real use surface. Beyond that, ongoing support is available on a monthly retainer.

Standard onboarding runs four to six weeks from kickoff to go-live. Enterprise implementations with custom objects and API integrations run eight to twelve weeks. We work in weekly sprints with a visible deliverable each week, so you are never waiting a month to see progress.

Yes. Sales Hub (pipelines, sequences, meetings, forecasting), Marketing Hub (forms, email, campaigns, lead scoring) and Service Hub (ticket pipelines, SLAs, knowledge base) are all configured according to your subscription tier and what your team will realistically use. We would rather ship three hubs configured well than five half-built.

Yes — role-based live training for sales, marketing, support and admins, plus recordings, written playbooks and a knowledge base your team keeps. Train-the-trainer sessions are available where you want internal ownership. Training is scheduled close to go-live so it lands when people can immediately apply it.

Yes, on Enterprise tiers we design custom objects such as Projects, Properties or Subscriptions with defined associations to standard objects. We also push back where a property or a labelled association would do the same job, because every custom object adds permanent complexity to imports, reporting and integrations.

We build scoring from your closed-won history rather than from opinion, split into fit and behaviour, then set thresholds where conversion actually jumps. Routing follows: round-robin, territory-based or weighted, with guardrails for out-of-office reps and a defined fallback when nobody matches.

Yes. We configure email sequences, task cadences, call scripts and in-CRM playbooks that log structured answers back to properties. Where you use SalesLoft or Outreach instead, we integrate rather than duplicate.

Yes. HTML templates, personalisation tokens and snippets are rebuilt in HubSpot with branding and dynamic fields tested against real records. Templates built for other platforms often need rework to render reliably across mail clients, and we flag that during discovery rather than after launch.

A comprehensive audit covers data quality (duplicates, fill rates, property sprawl), workflow efficiency and errors, integration and API health, user permissions, marketing contact usage and billing exposure, reporting accuracy and security settings. You receive a written report with findings ranked by cost and risk, plus a prioritised remediation plan.

An express audit takes three to five days. A comprehensive audit takes ten to twelve business days. Enterprise audits including API analysis and custom object review take three to four weeks. We also run a free 90-minute review that tells you which area needs attention without producing a full report.

Yes — super admin or read-only super admin access. We sign an NDA, make no changes during the audit and confirm that in writing before we begin. Marketing contact settings, API monitoring and permission review are not visible at lower access levels.

The recurring four are duplicate rates above 15%, workflows erroring or running with no exit criteria, marketing contact overages nobody chose, and misconfigured integrations quietly failing. Reporting disagreements almost always trace back to different date properties rather than to bad dashboards.

The audit and the remediation are separately priced, so you are free to take the report to another solution provider or handle it internally. Most clients engage us for the prioritised fixes, which we quote as a fixed-price scope once the findings are agreed.

Yes. We build REST and GraphQL connectors to ERPs such as NetSuite, SAP and Dynamics, billing platforms including Stripe, Zuora and Chargebee, and proprietary systems. Authentication, rate limiting, retry logic and error recovery are part of the build rather than an afterthought.

Yes — outgoing webhooks from HubSpot to your systems and incoming webhooks from third-party platforms into HubSpot, with payload transformation, signature verification and logging. Because delivery is at-least-once, handlers are built to be idempotent so repeated events do not create duplicate records.

Integrations are designed around HubSpot's limits, commonly 100 requests per ten seconds on standard tiers plus daily caps. We use batch endpoints, retry with exponential backoff and queueing for high-volume syncs, and we log every failure so gaps are visible instead of assumed.

Yes. We build real-time or scheduled two-way sync using webhooks and middleware, with explicit conflict resolution rules deciding which system wins per field and an audit trail of every write. Two-way sync without agreed conflict rules is how both systems end up wrong.

OAuth 2.0, private app tokens, JWT and basic auth where a legacy system requires it. Secrets are stored in a managed secret store, tokens are rotated, and no credentials are ever committed to code or shared over email.

Run a quarterly hygiene review covering duplicates, fill rates on decision-driving properties and unengaged marketing contacts, supported by automation that flags problems continuously. A full manual deduplication pass twice a year is usually enough once governance rules are in place.

Two scores rather than one: fit from firmographics, behaviour from activity, each on a 0–100 scale with behavioural decay after 30 days. Set thresholds where your historical conversion rate actually jumps rather than at round numbers, and write the contributing factors onto the record so reps can see why a lead scored what it did.

Authenticate the sending domain with SPF, DKIM and DMARC, warm new domains gradually, suppress contacts with no engagement in twelve months, segment by engagement, use double opt-in for cold sources and review complaint rates monthly. Deliverability is a hygiene discipline, not a one-off setup task.

A naming convention applied to every workflow, a documented owner per automation, a testing folder separate from production, and a quarterly review that disables anything with no enrolments. Portals past roughly fifty workflows need this to stay navigable — without it, people build duplicates because they cannot find the original.

HubSpot allows up to 1,000 custom properties per object, but usability degrades well before that. Under 300 is a reasonable ceiling for a mid-market portal. Archive unused properties, group related fields, and require a stated reporting or automation use case before any new property is created.

Fixed project pricing for defined scopes such as migration, onboarding and audit, and monthly retainers for ongoing consulting and managed services. Pricing is quoted after a discovery call, in a proposal that lists deliverables, assumptions and what is explicitly out of scope.

For fixed-price projects: 30% on signature to secure the schedule, 40% at the agreed midpoint milestone, and 30% on completion and sign-off. Larger engagements can be split across additional milestones. Retainers are invoiced monthly in advance.

Thirty days of hypercare covering bug fixes, user questions, minor adjustments and health monitoring, at no extra cost. After that, ongoing support runs on a monthly retainer, typically 10 to 20 hours a month for a mid-market portal.

Yes — retained engagements from around 10 hours a month up to a full fractional RevOps function, covering automation maintenance, reporting, data quality, enablement and roadmap. Most clients move onto a retainer after an implementation rather than instead of one.

Standard SLA is 24 hours for non-urgent requests and four hours for critical issues during business hours. Retained clients get a shared Slack channel with a two-hour target response. We cover UK and US business hours, which in practice means work happens overnight for US clients.

No — we are not a HubSpot Solutions Partner. We are independent HubSpot and RevOps solution providers. Our consultants are HubSpot-certified and have access to partner-level support channels and beta features where available, so implementation work is done by a certified team rather than learned on your portal.

Mostly teams between 10 and 250 people, in SaaS, professional services, healthcare technology and manufacturing. The common factor is having enough process complexity that CRM decisions matter, and a small enough team that a senior operator can work directly with decision makers.

The senior consultant you speak with on the discovery call does the implementation. There is no handoff to a junior delivery team after the sale, which is deliberate — it is also why we take on a limited number of concurrent engagements.