Migrate from Cronberry to Microsoft Dynamics 365 Sales

Cronberry Contacts map to Microsoft Dynamics 365 Sales Contact for qualified records and Lead for unqualified or early-stage records. We apply a split rule during scoping based on the customer's segment membership and engagement history: contacts assigned to a Sales-Qualified Smart Segment or with a completed call disposition migrate as Contacts attached to an Account; contacts in pre-qualification segments migrate as Leads. We preserve Cronberry's tag and segment associations as custom fields on both Lead and Contact so no audience context is lost during the split.

Cronberry Company records map to Microsoft Dynamics 365 Sales Account. The Company name becomes Account Name, and domain data maps to Account Website. We resolve the Contact-to-Account parent relationship during Contact import by matching Company ID or domain from the Cronberry export. Accounts are inserted before Contacts so that CustomerId lookups are satisfied at insert time.

Cronberry Campaigns carry channel type (Email, SMS, Push, WhatsApp), timing rules, and target segment assignments. We map each Campaign to a Microsoft Dynamics 365 Sales Opportunity with custom fields capturing the original Cronberry channel type and campaign status. The campaign goal and budget metadata migrate to Opportunity fields. Because Cronberry is marketing-centric and Microsoft Dynamics 365 Sales is sales-centric, we flag during scoping whether the customer's use of Campaigns corresponds to sales opportunities or to marketing campaign records that should be stored as Campaign (Dynamics) records with Opportunity linking handled separately.

Cronberry Smart Segments are defined by conditional field-value rules that cannot be exported as reusable schema. We reverse-engineer each segment's conditions by querying which contacts belong to each segment, then document the implied rules as a written segment specification. In Microsoft Dynamics 365 Sales , segments are rebuilt using Advanced Find queries or Dynamics 365 Marketing dynamic groups. We deliver the segment specification as a handoff document for the customer's Dynamics admin.

Cronberry Form field structures and conditional logic are extractable as schema. We map form fields to Microsoft Dynamics 365 Sales custom fields on Contact or to a custom entity if the form tracks a distinct record type. Visual layout, drag-and-drop positioning, and conditional visibility rules cannot be preserved automatically and must be rebuilt in Dynamics using the native form designer. We deliver a form field inventory mapping document for the admin to reference during rebuild.

Cronberry User and Agent records map to Microsoft Dynamics 365 Sales User. We match by email address during migration. Any Cronberry Owner or Agent without a corresponding Dynamics 365 User is placed in a reconciliation queue for the customer's admin to provision. Role and permission structures differ significantly between platforms; we migrate basic user identity and role assignment is handled by the admin post-migration.

Cronberry tracks behavioral events including email opens, link clicks, push interactions, and custom event types. We map these to Microsoft Dynamics 365 Sales Task records with custom fields capturing the event type, timestamp, and asset identifier. Event schema mapping is defined during scoping because Cronberry behavioral event schemas vary by customer implementation. We preserve event ordering by setting the Task ActivityDate to the original Cronberry event timestamp.

Cronberry message templates with personalization variables are migratable as content. We extract template body text, subject lines, and variable placeholders and map them to Microsoft Dynamics 365 Sales Email Template (for email) or custom text fields (for SMS and push). Rich HTML formatting may require post-migration cleanup in the Dynamics template editor. Sender ID and channel authentication credentials must be reconfigured in Microsoft Dynamics 365 Sales or the customer's email service provider post-migration.