请求提供从Sandbox环境到Production环境迁移CRM表的分步指导（无Azure Data Lake许可证）

Got it, let's walk through a robust, license-free step-by-step solution for migrating specific CRM tables from Sandbox to Production. Since you're new to this, I'll keep each step clear and actionable:

• First, list out exactly which tables you need to migrate (e.g., Account, Contact, custom tables like Project_Item). Make sure these tables have the same schema in both Sandbox and Production—double-check field names, data types, and required fields.
• Use your CRM's built-in schema comparison tool (most CRMs like Dynamics 365 have this natively) to confirm no schema mismatches that could break the migration.

• Use your CRM's native export feature (no extra tools needed):
  1. Navigate to the table you want to export in Sandbox.
  2. Go to the Export to Excel option (usually in the command bar).
  3. Choose Static Worksheet (to get a snapshot of current data) and select only the fields you need to migrate.
  4. Save the file as a .xlsx or .csv—stick with .csv for larger datasets since it’s lighter and easier to handle.
• For tables with related records (e.g., Contacts linked to Accounts), export parent records first, then child records to maintain relationships.

• Open the exported file and:
  • Remove any system-generated fields that shouldn’t be migrated (like CreatedOn, CreatedBy, RowVersion—these are auto-populated in Production).
  • Fix any data inconsistencies: check for missing required values, correct formatting issues (e.g., date formats, phone numbers), and remove duplicate records.
  • For lookup fields (like linking a Contact to an Account), replace the display name with the unique identifier (GUID) of the corresponding record in Production. If the parent record is also being migrated, use the GUID from the Sandbox export (you’ll map this later during import).

• Use your CRM's native import wizard:
  1. In Production, go to Advanced Settings > Data Management > Imports.
  2. Click Import Data and upload your cleaned .csv/.xlsx file.
  3. Map each column in your file to the corresponding field in the Production table. Pay extra attention to lookup fields—make sure you’re mapping to the correct GUID field.
  4. Choose the upsert option (if you want to update existing records and insert new ones) or insert (only add new records). This depends on whether the records already exist in Production.
  5. Run a test import first with a small subset of data to catch any errors before migrating the full dataset.

• After the import completes:
  • Check the import log for any failed records—fix the issues in your data file and reimport those records.
  • Spot-check a sample of migrated records to ensure all fields are populated correctly, and relationships between tables are intact.
• Run a quick report in Production comparing record counts to your Sandbox export to confirm no data was lost.

• If you need to repeat this migration regularly, you can use your CRM's built-in workflow or Power Automate (if available—no extra license needed for basic flows) to set up a scheduled export/import process:
  1. Create a flow that triggers on a schedule (e.g., weekly).
  2. Export the target tables from Sandbox to an online storage location (like OneDrive, which most organizations have access to).
  3. Clean the data using Excel Online actions in the flow.
  4. Import the cleaned data into Production using the CRM import connector.

内容的提问来源于stack exchange，提问作者Maët Faubert