Migrate from CRM.io by 500apps to Microsoft Dynamics 365 Sales

CRM.io Contact records (name, email, phone, company association, address) export directly as CSV rows and map 1:1 to Microsoft Microsoft Dynamics 365 Sales Contact. Email is used as the primary dedupe key. CRM.io Contact-to-Account links are preserved via the account_name or company_id column in the CSV, which resolves to the Account record inserted in the preceding phase.

CRM.io Lead records (name, source, status, owner, phone, email) map directly to Microsoft Dynamics 365 Sales Lead. Lead Status values from CRM.io map to the nearest equivalent Microsoft Dynamics 365 Sales leadstatus picklist value. Owner names resolve to Dynamics User records by email lookup against a customer-provided User list during scoping.

CRM.io Account/Company records (business name, industry, size, address) map to Microsoft Dynamics 365 Sales Account. Account is inserted before Contact to satisfy the parent Lookup relationship. We preserve the Account-Contact relationship using a compound key (AccountName + CompanyDomain) to reconstruct the primary contact link where the CRM.io CSV does not expose an explicit foreign key.

CRM.io Deals map to Microsoft Dynamics 365 Sales Opportunity. Deal stage, value, close date, owner, and associated Account name export from CRM.io. We reconstruct the Account-to-Deal link using the Account name column in the Deal CSV matched against the Account name in the Account CSV, resolving to the Account record inserted in the preceding phase. Closed-Won and Closed-Lost reasons from CRM.io map to Dynamics Opportunity CloseReason if present.

CRM.io pipeline stage names are configurable within the platform but have no public API to retrieve the active pipeline configuration. We infer stage order and names from the Deal records' stage values in the CSV export, then configure a corresponding Microsoft Dynamics 365 Sales Sales Process and stage values (StageName + Probability) before Opportunity import. The customer validates stage mapping during the scoping review.

CRM.io Activities (calls, emails, tasks, meetings) export as rows with activity type, subject, date, and linked Contact or Deal reference. The CRM.io CSV may not preserve the parent object ID reliably in the absence of an API. We reconstruct Activity-to-Contact associations using email subject matching and date proximity as a fallback, then insert Activities in dependency order after Contact and Opportunity so that WhoId and WhatId lookups resolve. Call activities map to Task with TaskSubtype = Call.

CRM.io Document Management stores file attachment metadata (filename, type, associated record) in the CSV. Binary files themselves do not export via CSV. We flag this during scoping and offer two options: a bulk binary file transfer via secure shared storage mapped to SharePoint document locations in Dynamics 365, or manual re-upload guidance for the customer post-migration. File metadata migrates as Note records with a reference to the target entity.

CRM.io Tags export as comma-separated values in the Contact and Deal CSV. We expand these into a multi-select picklist field in Microsoft Dynamics 365 Sales (custom field) or store as a semicolon-delimited text field if the destination org uses a lower Dynamics edition without multi-select support. The customer confirms tag strategy during scoping.

CRM.io assigns record ownership to Users identified by name. We extract every distinct Owner name from Contacts, Leads, Deals, and Activities and match against a customer-provided User email list for the destination Dynamics 365 org. Owners without a matching User are held in a reconciliation queue for the customer's admin to provision before record import resumes.

CRM.io explicitly states 'Customization Possible: No' in its published specifications. There are no documented custom fields, custom objects, or extended schemas in CRM.io. No custom field migration is required. This is a simplification compared to most CRM migrations, reducing the transformation complexity.