Migrate from Sales Creatio to HubSpot

Creatio contacts migrate as HubSpot contacts. Creatio stores name components as separate columns; HubSpot uses firstname and lastname properties. Email, phone, job title, and address fields map directly. The Creatio contact's primary account link becomes the HubSpot primary company association.

Creatio accounts map to HubSpot companies. Account name, website domain, industry classification, employee count, and annual revenue transfer directly. Creatio's parent-account hierarchy maps to HubSpot's parent company field when a company hierarchy exists in the source. Ensure that the parent-account relationship is validated before migration to avoid orphaned companies.

Creatio opportunities become HubSpot deals. Deal name, amount, expected close date, and stage transfer as the HubSpot dealname, amount, closedate, and dealstage properties. The Creatio opportunity owner links to the HubSpot deal owner via email match. If the opportunity owner email does not match a HubSpot user, assign a fallback owner to maintain data integrity.

Creatio opportunity stage pick-list values map to HubSpot deal stage names. Each Creatio stage maps individually; if stage names differ, a value-by-value lookup table is applied. Stage probability values are set per stage in HubSpot's pipeline configuration. Review the stage mapping table before migration to confirm that all stage names and probabilities align with your sales process.

Creatio activities map to HubSpot engagement records — calls and emails become engagement type 'email' or 'call', meetings become meetings, and tasks become tasks. Original timestamps, owners, and the parent record (contact, company, or deal) are preserved during migration. Verify that engagement types match HubSpot's allowed values to avoid import errors.

Creatio cases migrate as HubSpot tickets. Case subject, description, status, priority, and owner transfer to the corresponding HubSpot ticket properties. If Creatio uses a case pipeline with custom stages, those map to HubSpot ticket pipelines. Ensure the ticket pipeline stages are configured in HubSpot before migration to allow correct stage mapping.

Creatio custom entities map 1:1 to HubSpot custom objects when the HubSpot portal is on Enterprise or above. Custom entity column definitions become custom properties on the HubSpot custom object. Creatio entity relationships may require HubSpot association labels. Verify that the custom object schema in HubSpot includes all required properties and association labels before loading data.

Creatio BPM processes and automation workflows do not have a direct HubSpot equivalent and are not migrated. FlitStack AI exports the process definition JSON as a reference document so your HubSpot admin can rebuild the logic using HubSpot Workflows, Lists, and Automation tools.

Creatio file attachments associated with accounts, contacts, opportunities, or cases are downloaded and re-uploaded to HubSpot Files. Files are linked back to the corresponding HubSpot record. HubSpot file size limits (25MB per file) apply. Check that all file types are supported and that large files are split or compressed to meet HubSpot's size constraints before migration.

Creatio's N:N contact-to-account model — where one contact links to multiple accounts — maps to HubSpot's primary company plus secondary company associations. The most recently updated account association becomes the HubSpot primary company; remaining associations surface as secondary company links.

Creatio products from the product catalog migrate as HubSpot products, including product name, unit price, SKU, and description. Products already linked to opportunities map to HubSpot line items associated with the corresponding deal. Ensure that product SKUs are unique and that pricing information is up to date in Creatio before the migration to avoid mismatches in HubSpot.