Run the Segmentation Migration Utility and Review the Results

Use these steps in this topic to run the Siebel Segmentation Migration Utility and then review the results:

Here are the steps:

• Run the Migration Utility
• Enter Runtime Passwords
• Review the Terminal Command-line Summary
• Review the Audit Log
• Review the Campaign State after Migration
• Review Migrated Artifact in the OAS/OBIEE Catalog

Run the Migration Utility

Run the wrapper script from the extracted migration utility folder.

• Linux, Unix, or macOS:

  ./run-mktg-seg-migration.sh

  Windows:

  run-mktg-seg-migration.bat

• To add a log tag for easier log identification, use --tag:

  ./run-mktg-seg-migration.sh --tag MIGR

  run-mktg-seg-migration.bat --tag MIGR

• If the configuration file is stored outside the default config/application.properties location, pass it explicitly:

  ./run-mktg-seg-migration.sh --config/path/to/application.properties --tag MIGR

  run-mktg-seg-migration.bat --config C:\path\to\application.properties --tag MIGR

Note: The wrapper prompts for Siebel and OAS passwords at runtime. Don't pass those passwords in the command.

Enter Runtime Passwords

After the wrapper starts the migration utility, the command line prompts for the Siebel password and the OAS password. Enter the passwords when prompted.

Note: The password characters aren't visible while typing. This is expected terminal behavior.

The passwords are used only for the current migration run. They're not stored in application.properties or in the wrapper script.

Review the Terminal Command-line Summary

After the migration utility completes, review the terminal command-line summary.

The command-line summary includes this information:

Field	Description
Total campaigns	Number of campaigns evaluated in the run
Successful campaigns	Number of campaigns migrated successfully
Failed campaigns	Number of campaigns that did not complete successfully
Duration	Total runtime for the migration command

If any campaigns fail, review the application log and audit log in the next steps.

Review the Audit Log

Review the audit log to see migration activity at the campaign and artifact levels:

1. After the run completes, open the generated audit log from the logs folder.

   The audit log file uses this naming pattern: migration-audit-<timestamp>-<log-tag>.log.

2. Use the audit log to review migration activity at the campaign and artifact levels, including preprocessing, campaign discovery, transformation, campaign linking, and final migration status.
3. For detailed troubleshooting information, review the application log generated in the same logs folder: migration-<timestamp>-<log-tag>.log.

Review the Campaign State after Migration

After migration, open the campaign in Siebel Marketing and confirm the campaign now references the migrated Analysis-based artifact.

1. In the Analyses/Lists view, the campaign should show the migrated Analysis or Analysis Collection.
2. In the Allocation view, confirm that campaign allocation now points to the migrated Analysis or Analysis Collection.
3. After migration, the Segments/Lists view in the L4 menu should no longer display the previously associated Segment or List artifact.

Review Migrated Artifact in the OAS/OBIEE Catalog

Finally, review the migrated artifact.

1. Open the OAS/OBIEE Catalog and navigate to the source artifact folder.

2. Confirm that the migrated artifact is created with the M_ prefix, where M_ indicates a migrated artifact.