Informatica Migration Check List

By

Anvaya Akhouri
Wipro Technologies
September 2005
 MIGRATION CHECKLIST
Note: Migration is a critical process that directly impacts production.
Workflow
Names:
Mapping Names:

Migrated by : Migration Date:

Reviewed by : Review Date:

No of Migration errors : Cause :

No of Review errors : Cause :

New Errors (to be

included in the
checklist ) :

Sl. Checklist Item Yes/No/NA Actions To Be Taken/

No. Remarks
Analyze differences between Test and Production. List down any issues or missing information and
clarify with the development team before migration.
1. Are the number of sessions and other tasks in the
two environments equal and in the same order?
2. Does anyone have a lock on the sources?

3. Are the mappings and workflows valid?

4. Are the naming standards being followed?

5. Are the best practices being followed?

6. Are the database connections the same?

7. Do you have adequate information on what the new

DB Connections should be?
8. Are the pre and post session command tasks the
same?
9. Has the scheduling information been specified the
first run, the frequency, the time?
10. Are there any shortcuts for sources, targets or
mapplets?
11. Are the differences mentioned in the migration form
there in the mappings or workflows?
12. Is there any discrepancy between what is listed in the
migration form and what you can see in the
Informatica client?
13. Are you required to make any changes for scp to DW
or ftp to mainframes, etc and in which task?
14. Are the command tasks/ the scripts being called by
them using environmental variables?
15. Are there any scripts, sources or parameter files that
need to be copied to production?

INTERNALLY RESTRICTED Page 2 of 4

 MIGRATION CHECKLIST
Sl. Checklist Item Yes/No/NA Actions To Be Taken/
No. Remarks
16. Do operations need to be paged if the workflow fails?

17. Is there any reason not to suspend the workflow in

case of failure?
18. Are there any other special instructions?

Migrate from Test to Production. Please make sure that you do not make any unwanted changes e.g.
spelling mistakes, specifying incorrect script path, moving untested scripts, forgetting to change the
test mail recipient back to the production one, forgetting to delete command tasks when all
underlying commands have been removed, etc.
19. Have the list of objects to be migrated is verified
using Migration Request form?
(Sources, Targets, Transformations (reusable),
mapplets, mappings, sessions (reusable) and
workflows in order)
20. Have you created a new folder for that project with
the admin of the group as owner and given the
proper privileges on the folder?
21. Have the shortcuts for sources, targets or mapplets,
not already present in the shared folders been
moved?
22. Have you created any new database connection that
may need to be created?
23. Have you given appropriate permissions on the new
database connection?
24. For a SQL Server DBConnection, has the
appropriate information been added in the .odbc.ini
file?
25. If mapplets are involved, have you used import-
export for migration?
26. In case the change is only in the mapping logic, did
you refrain from moving the workflow? (You just need
to migrate the mapping and validate the workflow )
27. In case you need to create a new task (esp. session)
in a workflow, have you made sure that all the details
e.g. the sources, targets, database connections etc
are given correctly?
28. If it is an existing workflow with changes in both
mappings and workflows, have you moved the
changed mappings first, and then the workflow?
29. Have you changed the database connections?
30. Have you added any pre/post session command
tasks e.g. for scp to DW or ftp to mainframes that
may need to be added?

31. Have you changed any command tasks to call the

scripts? (Make sure you edit the path of the script to
point to the correct path. Do not edit the name of the
script.)

INTERNALLY RESTRICTED Page 3 of 4

 MIGRATION CHECKLIST
Sl. Checklist Item Yes/No/NA Actions To Be Taken/
No. Remarks
32. Have you changed the scripts on server being called
to use the Informatica Server directory variables?
33. Does the script have header information?

34. Are the comments in the scripts descriptive and up to

date?
35. Have you checked the Run if previous completed
check box in all command tasks?
36. Have you modified the workflow to suspend on error
(unless stated otherwise) ?
37. Have you modified the workflow to page to
operations if requested in the migration form?
38. Have you modified each session to send failure email
to operations in case of session failure?

39. In case you need to send email to more than one

user, have you separated the email ids by a comma?
( ; does not work in this case )
40. Have you taken care of any special instructions listed
in the migration form?
41. Have you checked in your changes, closed the
mappings and workflows and logged off?
42. Have you moved any parameter files that need to be
moved?
43. Have you moved any sources that need to be
moved?
44. Have you given the required permissions on any new
Unix folders you have created or any sources,
parameter files or scripts you have moved?
45. Are the session properties same as the developed
and tested version?
46. In case a common object has changed, have you
validated all the affected workflows, even though this
might not have been requested in the migration
form?

INTERNALLY RESTRICTED Page 4 of 4