Migrate from Customer Database App to HubSpot

Customer Database App contacts map directly to HubSpot contacts. The source's first name, last name, email, phone, mobile phone, job title, and address fields correspond to HubSpot's standard contact properties. HubSpot requires a lifecycle_stage value on every contact — we apply a default and flag any contact missing this data for manual review before migration.

Customer Database App companies map to HubSpot companies. HubSpot's company object holds name, domain (website), industry, number of employees, annual revenue, phone, and address. Parent-company hierarchies in Customer Database App map to HubSpot's Parent Company association — the parent must migrate before the child so the lookup resolves correctly.

Customer Database App deals map to HubSpot deal records. The deal name, amount, close date, owner, and custom fields transfer directly. HubSpot requires a pipeline assignment for each deal — we map the Customer Database App board to a HubSpot pipeline during the migration plan phase.

Customer Database App's Kanban board has a name, a set of stages (columns), and a display order. Each board becomes one HubSpot deal pipeline. Stage names become HubSpot stage names within that pipeline. If Customer Database App stores stage-level probabilities, those map to the HubSpot stage probability field; otherwise we apply HubSpot defaults.

Each Kanban column (stage) in Customer Database App becomes a HubSpot deal stage within the mapped pipeline. Stage order is preserved. Stage probability percentages transfer to HubSpot stage probability values. Close-date enforcement and forecast category derive from stage-level rules in HubSpot.

Customer Database App tags are flat, multi-select labels stored on any record type. Tags on contacts become a HubSpot custom multi-select contact property. Tags on companies become a HubSpot custom multi-select company property. We create the custom property in HubSpot before migration, map the exact tag values, and preserve the full list per record.

Customer Database App notes map to HubSpot engagement notes attached to the parent contact or company record. The note body, create timestamp, and owner email transfer. HubSpot engagement notes are associated to the contact or company via the engagements API.

Customer Database App tasks map to HubSpot tasks with subject, due date, owner, and completion status, preserving original timestamps and linking each task to the appropriate contact, company, or deal record. Calendar events map to HubSpot meetings with title, start/end times, owner, and attendees drawn from associated contacts or companies. Any unmatched owners or due dates are flagged before the final load.

File attachments on Customer Database App records are downloaded and re-uploaded to HubSpot's file storage. Files attach to the corresponding contact, company, or deal record. HubSpot file-size limits apply (default 10 MB per file for inline attachments; larger files require external hosting with a link stored as a custom property).

Customer Database App owner records are resolved by email match against HubSpot users. If a Customer Database App owner email has a matching HubSpot user, records assign to that HubSpot user automatically. Unmatched owners are flagged before migration — your team creates the HubSpot user first or assigns records to a fallback owner.