Migrate from Vaulta to HubSpot

Vaulta's vault_account record becomes a HubSpot Contact. The admin_wallet orEOA wallet address maps to a custom text field (wallet_address__c) since HubSpot has no native wallet-address field. If vault_profile contains a verified email, it maps to HubSpot's standard email field; otherwise email remains blank and the contact is identified by wallet address.

Vaulta token_transfer records have no native HubSpot equivalent — a custom object named Token_Transfer__c is created. Fields include tx_hash, value, from_address, to_address, token_address, timestamp, gas_used, and gas_price_gwei. The associated sender and receiver wallet_address contacts are linked via HubSpot's association model.

If Vaulta stores an organization or vault_family name alongside vault_account records, it maps to a HubSpot Company. For single-vault setups, the vault name becomes the Company Name; for multi-vault organizations, each vault_account with a unique vault_name creates a separate Company record.

Vaulta's current token balance per wallet address has no HubSpot standard equivalent. A Token_Balance__c custom object captures wallet_address, token_symbol, balance, and usd_value. The associated Contact is linked via HubSpot association so balance data surfaces on the contact record. Balance snapshots are captured at migration time to establish a baseline for reporting.

Vaulta smart_contract_interaction records map to a Smart_Contract__c custom object capturing contract_address, contract_name, network, function_called, caller_address, block_timestamp, and transaction_hash. Smart contract deployments in Vaulta are stored as records for audit reference rather than as native CRM objects. This mapping supports compliance auditing and smart contract interaction tracking within your CRM.

Vaulta NFT transfer events become an NFT_Transfer__c custom object with token_id, contract_address, from_address, to_address, transaction_hash, block_timestamp, and token_uri. NFT ownership at migration time is stored as a separate NFT_Holding__c custom object linked to the owning Contact. The NFT_Holding__c object stores the current owner at migration time for historical reference.

If Vaulta's vault_profile contains name, email, or kyc_status linked to a wallet address, that data maps to the corresponding HubSpot Contact's standard properties (firstname, lastname, email) plus custom kyc_status__c. Unlinked wallets remain as contacts identified by wallet address only. This enables KYC status tracking within HubSpot for compliance purposes.

Vaulta NFT collection metadata (collection_name, contract_address, total_supply, description) maps directly to NFT_Collection__c fields. Individual NFT records link to their collection via a lookup field on the NFT_Transfer__c and NFT_Holding__c objects. This hierarchical structure allows you to run collection-level analytics, track total supply trends, and manage NFT portfolio performance within HubSpot's reporting tools.

Every migrated record receives a source_system_id__c custom field storing the original Vaulta record identifier (tx_hash for transactions, wallet_address for contacts, contract_address for smart contracts). This enables delta-run de-duplication, audit trails, and cross-referencing Vaulta history post-migration. This field is essential for maintaining data lineage and supporting future data governance initiatives.

Vaulta's on-chain associations (sender-to-receiver in token_transfer, owner-to-NFT in nft_transfer) are preserved as HubSpot Contact-to-Contact associations or as lookup fields on custom objects. Multi-wallet accounts use a junction object to link one Contact to multiple wallet_address records. This ensures that relationship data from on-chain interactions is fully preserved and queryable within HubSpot's association model.