The process of migrating from a Revenue Conduit account to a Unific account
What to expect:
- Sign up for Unific and connect your store and HubSpot
- Unific will create properties in HubSpot for Unific. All Unific custom properties end with " - Unific" (For example: "Products Bought - Unific). Properties are listed here.
- Properties that were created by Revenue Conduit will be left as-is
- To update all properties, you will need to request a Historical Data Sync. However, please read the rest of this article before you request it.
- Since Unific syncs different properties than Revenue Conduit, you will need to change your workflows to use the newer properties to ensure they still function as expected.
- Identify all workflows using Revenue Conduit properties and remove and re-add the filters so that they use the correct method for the matching Unific property (for example, an enum property may usually use "any of" but a text property uses "any")
- Find deprecated (Revenue Conduit) properties in workflows and lists and update them with their Unific equivalent, and change their label to include [DEPRACATED] at the beginning of the label so that your team doesn't try and use outdated Revenue Conduit properties.
- Delete these deprecated (Revenue Conduit) properties when it is convenient for you.
- After this migration of workflows and lists to the Unific properties is done, request a Historical Data Sync.
- After Unific is installed and operational, remember to cancel your Revenue Conduit account. You can request cancelation by submitting a ticket.
What will be changed?
Contact:
- The property "current_abandoned_cart" will now have options "Yes", which corresponds to the value "true" and "No", which corresponds to the value of "false".
- These properties will be deleted, and new ones will be created with type "multiline text":
Property Label | Old Property Name (RC) | New Property Name (Unific) |
Categories Bought | categories_bought | categories_bought_text |
Products Bought | products_bought | products_bought_text |
Product Types Bought | product_types_bought | product_types_bought_text |
SKUs Bought | skus_bought | skus_bought_text |
Vendors Bought | vendors_bought | vendors_bought_text |
Coupon Codes Used | coupon_codes_used | coupon_codes_used_text |
Shopify Product Tags | shopify_product_tags | shopify_product_tags_text |
Shopify Customer Tags | shopify_customer_tags | shopify_customer_tags_text |
Last Categories Bought | last_categories_bought | last_categories_bought_text |
Last Products Bought | last_products_bought | last_products_bought_text |
Last Product Bought | last_product_bought | last_product_bought_text |
Last Product Types Bought | last_product_types_bought | last_product_types_bought_text |
Last SKUs Bought | last_skus_bought | last_skus_bought_text |
Last Vendors Bought | last_vendors_bought | last_vendors_bought_text |
Abandoned Cart Products | abandoned_cart_products | abandoned_cart_products_text |
Abandoned Cart Categories | abandoned_cart_categories | abandoned_cart_categories_text |
- These properties will be named the same, but the field types will be modified:
Property Label | New Type | New Type |
Abandoned Cart Date | date | datetime |
Last Order Shipment Date | date | datetime |
First Order Date | date | datetime |
Last Order Date | date | datetime |
Account Creation Date | date | datetime |
Coupon Code Campaign X Expiration Date | date | datetime |
Last Order Status | enum select | string (textarea) |
Last Order Fulfillment Status | enum select | string (textarea) |
Last Order Shopify Order Source | enum select | string (textarea) |
Customer Group | enum select | string (textarea) |
Deal:
- These properties will be named the same, but the field types will be modified:
Property Label | Old Type | New Type |
Shipment Date | date | datetime |