Migrate from RAYNET CRM to HubSpot

Raynet Contact maps to HubSpot Contact as a direct 1:1 object mapping. All standard contact fields (name, email, phone, address) map to HubSpot's built-in contact properties. Raynet's primary company association maps to HubSpot's primary company link. Original create and update timestamps are preserved as HubSpot custom datetime properties since HubSpot's native Createdate reflects the migration timestamp.

Raynet Company maps to HubSpot Company directly. Company name, domain/website, industry, employee count, and annual revenue map to HubSpot's equivalent built-in company properties. Raynet's parent-company hierarchy maps to HubSpot's parent company association on the Company object. Multi-company associations (Raynet N:N contact-company model) are surfaced as HubSpot secondary company associations.

Raynet Deal maps directly to HubSpot Deal. Deal name, amount, close date, and owner map to HubSpot's built-in deal properties. The original Raynet deal identifier is stored as a custom property (Raynet_Deal_ID__c) for traceability and delta-run de-duplication. Stage names are mapped using value-by-value stage mapping against HubSpot pipeline stages.

Raynet's pipeline concept maps directly to HubSpot's deal pipeline. Each Raynet pipeline maps to a corresponding HubSpot deal pipeline. If Raynet uses multiple pipelines, each becomes a separate HubSpot pipeline object. HubSpot Professional and above support multiple pipelines natively, so this mapping requires no additional licensing on the destination side.

Raynet pipeline stages map to HubSpot pipeline stages using per-pipeline value mapping. Stage names are mapped individually — if Raynet uses 'Proposal Sent' and HubSpot pipeline uses 'Presentation Scheduled', the mapping preserves the stage name as a custom field (Original_Stage__c) while routing the deal to the correct HubSpot stage. Stage-entered timestamps are preserved as HubSpot custom datetime fields.

Raynet deal types (one per deal on Start, up to 5 on Professional, unlimited on Enterprise) have no native HubSpot equivalent. We create a HubSpot custom deal property called Deal_Type__c and migrate each Raynet deal type value as a HubSpot pick-list value. If a Raynet deal had multiple types, all are stored comma-separated in Deal_Type__c. This property is available for HubSpot reporting, workflows, and list segmentation after migration.

Raynet owner (sales rep assigned to contact, company, or deal) maps to HubSpot user by email match. We resolve each Raynet owner email against HubSpot's user list — matched users receive ownership automatically. Unmatched owners are flagged before migration runs; your team either creates a HubSpot user or assigns those records to a fallback owner before the migration commits.

Raynet activities — calls, meetings, and notes — map to HubSpot engagements. Call logs become HubSpot call engagements with original timestamps and owner links. Meetings become HubSpot meeting engagements with duration, attendees, and start/end times preserved. Notes become HubSpot notes attached to the relevant contact, company, or deal record. Original activity timestamps and owner assignments are preserved on each engagement record.

Raynet custom properties from all tiers migrate as HubSpot custom properties. We create each property in HubSpot with the appropriate type — pick-list values become HubSpot pick-list properties, dates become datetime properties, and text fields become text properties. On Raynet Enterprise accounts with 500 custom fields, we map all 500 to HubSpot custom properties; all HubSpot paid tiers support unlimited custom properties so no tier constraint applies on the destination side.

Raynet file attachments associated with contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files. Files are re-attached to the corresponding HubSpot record. File size limits apply — HubSpot's import supports files up to the platform's file storage limits per account tier. Inline images in notes are downloaded, rehosted, and the note is updated with the new URL.