Migrate from webCRM to HubSpot

webCRM Person records map to HubSpot Contacts. webCRM Organisation link on the Person becomes the HubSpot primary company association. If a Person has no linked Organisation in webCRM, it lands in HubSpot as a Contact with no primary company — your team assigns it in HubSpot after migration.

webCRM Organisation maps directly to HubSpot Company. Company name, domain, address fields, and industry values map field-by-field. webCRM industry pick-list values are reviewed against HubSpot's default industry pick-list — non-matching values are stored as a custom property and mapped during setup.

webCRM Deals map to HubSpot Deals. The deal name, amount, currency, and close date migrate directly. The webCRM pipeline name is stored as a source_pipeline custom property so your team can create HubSpot pipelines matching the source structure before assigning deals.

webCRM deal stages are free-text per pipeline with no enforced pick-list. Each webCRM stage name maps to a corresponding HubSpot stage value by name — stages that don't exist in HubSpot yet are created as part of the pipeline setup before data loads. We validate all stage values before committing the migration.

webCRM's product database has no direct HubSpot equivalent. Product names and unit prices linked to webCRM deals are extracted and surfaced in the migration plan as a rebuild reference. Your team creates the HubSpot Product Library entries; we provide the mapping from webCRM product IDs to deal line items.

webCRM custom fields for Person, Organisation, and Deal become HubSpot custom contact/company/deal properties. Custom fields with pick-list types require value-by-value mapping against HubSpot pick-list options. We create the HubSpot custom properties before data loads so all custom field data lands in the correct fields.

webCRM logged calls, emails, meetings, notes, and tasks migrate to HubSpot engagements with original timestamps, owners, and parent-record links preserved. Call logs and emails become HubSpot engagements logged against the Contact or Deal. Meeting records preserve start/end time and location.

webCRM file attachments on Person, Organisation, or Deal records are extracted and re-uploaded to HubSpot Files, then linked back to the parent record. Files are rehosted in HubSpot's file storage. There is a 25 MB per-file limit in HubSpot — files above that threshold are flagged for manual handling.

webCRM Person records can have an assigned owner. Owner resolution happens by matching the webCRM owner's email address to an existing HubSpot user. Unmatched owners are flagged before migration — your team either creates the HubSpot user first or assigns the records to a fallback owner.

webCRM stores deal amounts in multiple currencies with conversion metadata. HubSpot stores a single currency amount per deal. We preserve the original webCRM currency code and amount as custom properties on the HubSpot deal, then map the converted amount to the standard Amount field.

The webCRM internal record ID is stored as a custom property on each HubSpot record for traceability and to support delta-run deduplication. This allows FlitStack to identify which records were already migrated during the delta-pickup window and avoid creating duplicates.