Considerations if Performing Repeat Migration
This section describes factors to consider if a migration needs to be repeated.
Caution
It is not a recommended practice to repeat migrations, and we strongly recommend following our two-day migration process described in Migration Steps and Best Practices.
For example, you may need to repeat the migration if configuration and translation changes were made in CI Desktop before your CI SaaS migration if fully completed.
Below is a summary of these how the import process works differently for subsequent translation and configuration imports.
Summary of behaviors if you repeat the import
If you repeat the imports (after the initial import) of the configuration and translation files to CI SaaS, you will want to understand how the imports behave for each file type.
| Configuration Type | Behaviors | Key Notes |
|---|---|---|
| Global Configurations | Replaces all contents | Entire configuration is overwritten with the imported file. |
| Column Configurations | Replaces all contents for each output file | Only the specific output fields in the import are replaced. |
| Account Translations | Insert/Merge, No Deletes | Existing translations are updated if the import file has different values. Absent translations in the import file are NOT deleted from CI SaaS. |
| Security Translations | Insert/Merge, No Deletes | Existing translations are updated if the import file has different values. Absent translations in the import file are NOT deleted from CI SaaS. |
Detailed behaviors for Account Translations and Security Translations imports
-
Account Translations: Insert/Merge (No Deletes)
- Matching Behavior
If an account translation for the same account ID exists:- The system checks these fields:
- Output Account Identifier
- "Import Enabled/Include Override" Flag
- "Export Positions If Stale" Flag
- MM Symbol and MM Symbol Type
- If all fields match (case-insensitive), no changes are made.
- If any field differs, the existing translation is updated and the change is logged as "overwritten."
- The system checks these fields:
- Absent Translations:
Translations that are absent from the import file are NOT deleted from CI SaaS.
- Matching Behavior
-
Security Translations: Insert/Merge (No Deletes)
- Matching Behavior
- The system identifies existing translations based on Ticker, CUSIP, or Name.
- If a match is found, these fields are checked:
- Output Symbol
- Output Security Type
- Reference Name
- If all fields match, no changes are made and this is logged as "ignored."
- If any field differs, the existing translation is updated, and the change is logged as "overwritten."
- Absent Translations
Translations absent from the import file are NOT deleted from CI SaaS.
- Matching Behavior
Updated about 16 hours ago