Migrate from CentralStationCRM to Microsoft Dynamics 365 Sales

CentralStationCRM People map to Microsoft Dynamics 365 Sales Contact records. Every Contact requires a parent AccountId at insert time, so we build the Account (from Companies) before Contact migration begins. The CentralStationCRM email, phone, job title, and custom field values map to the matching Dynamics Contact fields. We use the Dynamics 365 Web API (POST /contacts) with OData batching for efficiency, respecting the source rate limit by chunking requests at 40 per 10-second window.

CentralStationCRM Companies map directly to Microsoft Dynamics 365 Sales Account records. The Company name becomes Account Name; website and address fields map to the standard Account fields. We resolve the CentralStationCRM company-to-person relationship as a 1-n Contact-to-Account linkage by matching person.company_id to the exported Company ID. If the source CentralStationCRM account has no companies, we create a default Account named after the organisation for all contacts to attach to.

CentralStationCRM Deals map to Microsoft Dynamics 365 Sales Opportunity records. The Deal value maps to Amount; stage maps to the configured Sales Process stage name; assignee maps to the OwnerId resolved via CentralStationCRM owner-to-Dynamics-User email matching. Deals linked to both a Person and a Company produce Opportunities with both ContactId and AccountId resolved. We create Opportunity records before the Contact import phase completes so that the AccountId lookup is already validated at insert time.

Each CentralStationCRM deal stage from the source account's pipeline configuration maps to a named Stage value in a Microsoft Dynamics 365 Sales Process that we configure during schema design. If CentralStationCRM uses custom stage names, we create matching Dynamics stage values rather than reusing a default pipeline. Stage probability percentages map to StageProbability on each stage definition. We do not alter the Dynamics default pipeline unless the customer requests a custom Sales Process.

CentralStationCRM Leads map to Microsoft Dynamics 365 Sales Lead records. The Lead status, source, and any custom fields transfer directly. We do not auto-convert CentralStationCRM Leads to Contacts during migration; that step belongs to the customer's sales team post-cutover. If Microsoft Dynamics 365 Sales Professional is the destination tier, the Lead object is available and we use the standard Lead-to-Contact convert workflow post-migration.

CentralStationCRM Activities attached to People or Companies export via nested routes (GET /api/people/{id}/activities.json and GET /api/companies/{id}/activities.json). Call activities map to Task records with TaskSubtype = Call; meeting activities map to Event records with StartDateTime and EndDateTime preserved; notes map to Annotation (Note) records linked via the Regarding field to the parent Contact or Account. We preserve the original activity timestamp as ActivityDate on the Task or Event record so the chronological timeline is intact in Dynamics.

CentralStationCRM Tasks attached to People or Deals map to Microsoft Dynamics 365 Sales Task records. Task title maps to Subject, due date maps to ActivityDate, and completion state migrates as the Status field (Open = Open, Completed = Completed). We do not delete completed tasks; their Status field carries the original state so the task history is preserved rather than lost at migration.

CentralStationCRM Offers (line-item documents attached to People or Companies) map to Microsoft Dynamics 365 Sales Quote records. The offer total and line items migrate as QuoteDetail (OpportunityLineItem equivalent) records. We resolve the Regarding (parent) reference on each Quote to the matching Opportunity or Account created earlier in the migration sequence. If the destination is Microsoft Dynamics 365 Sales Professional or above, the Quote object is available without additional configuration.

CentralStationCRM addresses are 1-n child records fetched via GET /api/people/{id}/addrs.json. We walk every nested address route during export and write each address to Microsoft Dynamics 365 Sales CustomerAddress records linked to the parent Contact or Account. The primary address flag from CentralStationCRM maps to the AddressNumber field on CustomerAddress. If the Dynamics edition does not include CustomerAddress, we attach address fields directly to the Account or Contact record using the standard address composite field.

CentralStationCRM tags are flat key-value labels stored per record. We export all tag assignments and create matching msdyn_tag records in Microsoft Dynamics 365 Sales . Each tag assignment on a Contact, Account, or Opportunity creates a msdyn_tagassignment record linking the tag to the entity. If the customer requires a taxonomy hierarchy beyond flat tags, we recommend using Dynamics Topics post-migration; the flat tag vocabulary is preserved as-is during migration.

CentralStationCRM tenants define their own custom fields with no fixed schema. We discover every active custom field on People, Companies, Deals, and Leads during scoping, determine the equivalent Dynamics 365 data type (string, integer, decimal, picklist, boolean), create the matching custom field on the appropriate Dynamics entity during schema design, and map the values during the data phase. Custom field creation is completed in a Dynamics Sandbox before production migration.