Although, there are many tools/provisions which you can use to migrate data in one-go which also helps you retain or take over the original GUIDs from source instance to target instance.
Let’s look at this scenario –
- You have a Source Environment (https://chcft166.crm.dynamics.com/) from which you want to move data over to the Target environment (https://cft166sales.crm.dynamics.com/).
- Now, you want to move Accounts from the Source to Target environment and also want to retain the GUIDs from the Source environment.
- Let’s note the Source GUID in a Notepad just to show an example –
- Now, when we export these records and import into the Target instance, the source GUID should be retained. Let’s look in below sections as to how we can achieve this.
Export to Dynamic Sheet
Here’s how you use Export to Dynamic Sheet in order to also get supporting fields to be imported into Production –
- In your desired view, expand on Export to Excel option and look for Dynamic Worksheet.
- Select the fields you need and click on Export.
- When you Export, you’ll get the Excel file in your system. Open it up!
- Just notice that there are 3 hidden fields in the Excel which have other data stored in them. The Excel columns start from “D” instead of “A”.
- And when you expand the columns, you’ll see the A, B & C as well. Now, A column has the GUID which you need to be set in the Target instance.
- Save this file as .CSV in case this is .XLS
Import into Target Instance
Once you have saved the File in .CSV, let’s import the CSV into the Target instance –
- In any view, expand on Import (Look in the Ellipses menu).
- You’ll find the Import from CSV button.
- Now, choose File by clicking on this button and selecting the File from your system.
- Once the File is selected, click on Next.
- Proceed further if you don’t wish to change any other preferences.
- In Mapping, you can see the fields from the Excel file i.e. (Do Not Modify) Account which is Not Mapped.
- Then, for this field look for the Primary Key field of the entity in question. Account’s Primary Key field in this example.
- Once this is mapped, you can Finish Import.
- Once you Finish Import and check back and open the Imported record.
- When you open the Imported record, look at the GUID of the record itself.
- If I click on the URL and see the end of the URL, I’ll have the same GUID as the Source record from the Source environment.
And when you try to match the GUID, you’ll find the same GUID on the target instance.
And that’s how you can Excel Import / Export without other tools to move data with source GUIDs to the Target GUIDs.
Hope this was useful!
Here are some Power Automate posts you want to check out –
- Select the item based on a key value using Filter Array in Power Automate
- Select values from an array using Select action in a Power Automate Flow
- Blocking Attachment Extensions in Dynamics 365 CRM
- Upgrade Dataverse for Teams Environment to Dataverse Environment
- Showing Sandbox or Non Production Apps in Power App mobile app
- Create a Power Apps Per User Plan Trial | Dataverse environment
- Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
- Co-presence in Power Automate | Multiple users working on a Flow
- Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
- Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
- Call a Flow from Canvas Power App and get back response | Power Platform\
- FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
- Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
- Asynchronous HTTP Response from a Flow | Power Automate
- Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
- Converting JSON to XML and XML to JSON in a Flow | Power Automate