Migrate from Getfly CRM to Microsoft Dynamics 365 Sales

Getfly's primary object is an Account that stores both organizational records and individual contacts without a clear separation. We inspect each record at migration time: records with a domain in the email field, a company phone without a personal name, or no individual name map to Microsoft Microsoft Dynamics 365 Sales Account. Records with an individual name, personal email, and a linked company name map to Dynamics Contact with the AccountId lookup resolved to the parent Account. This split requires two-pass resolution: first pass identifies all organizational accounts, second pass distributes individual records into the Account-Contact hierarchy. We flag any Getfly Account record with ambiguous type for customer review before migration.

Getfly Products with SKU, pricing, and detail_custom_fields map to Microsoft Dynamics 365 Sales Product2 records. The detail_custom_fields nested object from Getfly flattens into typed custom fields on Product2. Standard Price Book entries are created during import to enable Opportunity Product line items. ProductCode migrates from Getfly's SKU field, and the product pricing tiers (if Getfly supports volume pricing) map to PricebookEntry records per price book.

Getfly Deals map to Microsoft Dynamics 365 Sales Opportunity. Each Getfly pipeline becomes a Microsoft Dynamics 365 Sales Process (a stage whitelist) and an Opportunity Record Type that we configure before migration. Stage names from Getfly map to StageName values in Dynamics, and probability percentages round to Dynamics-allowed integers. Closed-Lost and Closed-Won statuses from Getfly map to equivalent Dynamics stage outcomes. Deal amount, close date, and owner assignment migrate directly.

Getfly Activity records map to Microsoft Dynamics 365 Sales Task and Event objects based on activity type. Call activities map to Task with TaskSubtype = Call and CallDirection preserved. Meeting activities map to Event with StartDateTime, EndDateTime, and Location fields carried over. Task activities map to Task with Status, Priority, and ActivityDate preserved. All activity records resolve their Getfly owner reference to a Dynamics 365 UserId via the User mapping table, and the associated Account or Contact lookup resolves via the Account-Contact split completed in phase one.

Getfly PABX call logs store a recording URL rather than the audio file itself. We download each recording file at export time to local storage before the migration window closes. Recordings re-upload to Microsoft Dynamics 365 Sales as Notes attached to the Task record, or as file attachments on the related Account or Contact. If the PABX system is also replaced during the cutover, recording continuity requires explicit scoping to ensure the source recording URLs remain accessible during the download phase. We flag this risk during discovery and request confirmation that recording files are downloaded before any Getfly account suspension.

Getfly custom fields on Account and Product records map to custom fields on the corresponding Microsoft Dynamics 365 Sales objects. Getfly does not publish a field schema endpoint, so we discover custom fields by sampling Getfly API records during the export phase. We request the customer to run a full field audit report from Getfly's admin panel before migration kickoff to catch rarely-used fields that sampling may miss. Field type mapping converts Getfly field types (text, number, dropdown, date) to equivalent Dynamics field types, and any unsupported field type is flagged for customer decision on how to represent it.

Getfly Users acting as record owners map to Microsoft Dynamics 365 Sales User records. We extract every distinct owner referenced on Account, Deal, and Activity records and match by email address against the destination Dynamics 365 tenant. Owners without a matching Dynamics User go into a reconciliation queue. The customer's Dynamics 365 admin provisions any missing Users before production migration begins. Getfly role and permission structures do not map directly to Dynamics security roles; we document the Getfly role list and map it to a recommended Dynamics security role matrix for the customer's admin to configure post-migration.

Attachments referenced by URL on Getfly Account or Product records are downloaded to local storage during export and re-uploaded to Microsoft Dynamics 365 Sales . In Dynamics, file attachments can live as Note records with file body, or be linked to SharePoint document management if the customer's Dynamics environment has SharePoint integration configured. We map each Getfly attachment to the parent record (Account, Contact, or Product) via a lookup resolution. Attachments larger than 25 MB are flagged for the customer to decide on chunked upload strategy.

Getfly Marketing Campaigns with name, start/end dates, and linked accounts map to Microsoft Dynamics 365 Sales Campaign records. Campaign member accounts (which Getfly accounts were contacted as part of each campaign) are preserved as CampaignMember records linked to the parent Campaign and the resolved Dynamics Account. Campaign member status from Getfly maps to CampaignMember Status values. Note that Getfly campaign-level engagement metrics (opens, clicks, responses) do not have a direct Dynamics equivalent and are preserved as campaign notes if available via API.