summaryrefslogtreecommitdiffabout
path: root/bin/Migration-HowTo.txt
Unidiff
Diffstat (limited to 'bin/Migration-HowTo.txt') (more/less context) (ignore whitespace changes)
-rw-r--r--bin/Migration-HowTo.txt386
1 files changed, 386 insertions, 0 deletions
diff --git a/bin/Migration-HowTo.txt b/bin/Migration-HowTo.txt
new file mode 100644
index 0000000..0fc7f70
--- a/dev/null
+++ b/bin/Migration-HowTo.txt
@@ -0,0 +1,386 @@
1
2Migration HowTo Outlook 200X -> KDE
3
4Version 1.0.2
5The latest version of this file can be downloaded from
6http://sourceforge.net/projects/kdepimpi/
7Please choose there package/project/file:
8general Files for KDE/Pim
9MigrationHowTo_OL2KDE
10MigrationHowTo_OL2KDE.txt.zip
11
12
13This HowTo describes the process of migrating data ( contact and calendar data ) from Outlook 200X to the PIM programs of the KDE-Desktop-Environment.
14The PIM programs are KAdddressbook and KOrganizer, which may be used embedded in the Kontact PIM management framework.
15This HowTo describes version 1.9.3a of the migration tools.
16The migration tools are the platform independent versions of KAdddressbook and KOrganizer: KAdddressbook/Pi and KOrganizer/Pi.
17
18Content:
19
201) How to start
212) How to import pst files in Outlook
223) Where to get the migration tools
234) How to install the migration tools
245) How to get the contact data out of Outlook200X
256) How to get the calendar data out of Outlook200X
267) How to import your contact data into Kontact
278) How to import your calendar data into Kontact
28
29APPENDIX A) Problems and solutions when reading contact data
30APPENDIX B) Problems and solutions when reading calendar data
31
32****************************************
331) How to start
34****************************************
35
36For the migration we need the actual Outlook 200X data, which Outlook stores in *.pst files.
37Then we need an installed version of Outlook 200X to access these *.pst files.
38When we have an Outllook 200X running with all data accessable, we need the migration tools.
39
40If you have no Outlook200X installed please install the Outlook version, you need to a import your *.pst files.
41If you have an Outlook200X installed with no contact/calendar data available, and you have some *.pst files please continue with: 2) How to import pst files in Outlook.
42If you have a running Outlook200X already with contact/calendar data available, please continue with: 3) Where to get the migration tools.
43
44
45****************************************
462) How to import pst files in Outlook
47****************************************
48
49To open a local *.pst file in Outlook2003, choose menu:
50File - Open - Outlook Data File ...
51Now the data included in this file is shown
52as folders of a newly added root folder in the Outlook folder view.
53This root folder is probably not accessable from
54the migration tools via OLE.
55To access data stored in one of the subfolders,
56copy this subfolder to a root folder,
57which can be accessed from the migration tools via OLE.
58(To know, which folder can be accessed, just perform 5.) or 6.) until
59you get the Oulook import dialog!)
60
61To copy it, right click on that subfolder and choose
62Copy "<subfoldername>"...
63in the popup menu.
64
65****************************************
663) Where to get the migration tools
67****************************************
68
69The data migration is is performed with the Windows versions of KAdddressbook/Pi and KOrganizer/Pi.
70Pi stands for platform-independend - platform-independend because the same program is available for different platforms, like Windows, Linux desktop and Sharp-Zaurus PDA.
71Note: The Linux desktop versions of KOrganizer/Pi and KOrganizer/KDE-desktop are two different programs! You cannot use KOrganizer/Pi together with, or embedded in, the KDE-desktop environment. The same is valid for KAdddressbook/Pi.
72
73The programs you need for the migration are:
74a) KAdddressbook/Pi executeable + 2dlls + icons
75b) KOrganizer/Pi executeable + icons
76c) The Qt3 library qt-mt331.dll and the MSVC library msvcr71.dll and the MSVC library mfc71u.dll
77You can download all of them at:
78
79http://sourceforge.net/projects/kdepimpi/
80
81Download of a) and b)
82Please choose there package/project with name KDE/Pim
83(Direct link: http://sourceforge.net/project/showfiles.php?group_id=104103&package_id=112604 )
84Choose there the topmost latest version and the files
85kapixxx-exe.zip
86kopixxx-exe.zip
87The latest version is currently ( 2004-07-13 ) 1.9.3a.
88Such that the files to download are
89kapi193a-exe.zip
90kopi193a-exe.zip
91
92To download c)
93Please choose there package/project/file:
94general Files for KDE/Pim
95Needed Windows Dlls
96kdepimdll.zip
97
98(Direct link: http://sourceforge.net/project/showfiles.php?group_id=104103&package_id=122438&release_id=256700 )
99Choose there the file:
100kdepimdll.zip
101
102Now you have downloaded the files
103
104kapi193a-exe.zip
105kopi193a-exe.zip
106kdepimdll.zip
107
108and we can continue to install the files, which is simply unzipping them.
109
110
111****************************************
1124) How to install the migration tools
113****************************************
114
115You have downloaded the files
116
117kapi193a-exe.zip
118kopi193a-exe.zip
119kdepimdll.zip
120
121Unzip these files.
122Now choose an arbitrary installation directory, where to copy all the needed files together.
123You should have now the following files and the directory "kdepim" in the same directory:
124kopi.exe
125kapi.exe
126microkabc_dir.dll
127microkabc_file.dll
128msvcr71.dll
129mfc71u.dll
130qt-mt331.dll
131ReadMich.txt
132kdepim (directory)
133
134The directory "kdepim" should contain subdirectories
135kaddressbook
136korganizer
137which itself contain some subdirectories with icons and help text.
138
139Now the migration tools are ready for use.
140
141
142NOTE AND HINT for performing migration on many workstations:
143Just burn the content of the installation dir on a CD.
144Then you can put the CD in every workstation and execute the migration tools from that CD directly.
145
146
147*************************************************************
1485) How to get the contact data out of Outlook200X
149*************************************************************
150
151Note: When accessing Outlook to read the data, it should not be possible, that there is any data lost in Outlook, because the progam accesses Outlook only Read-Only.
152
153You have the file
154kapi.exe
155and the other needed files accessable on your workstation.
156
157Getting the contact data
158
159Please start kapi.exe.
160Choose menu:
161File - Import - Import from OL...
162You will get a dialog which shows all "Personal Folders" of Outlook.
163Choose the Contact Folder(s) you want to import and select them with a hook.
164(All other folder but the contact containing folders are shown, but disabled).
165(If the data you want to import is not stored in one of the shown folders,
166please read step 2.) and click on "close" ).
167Click the "import" button.
168Now Outlook asks you to allow access to the contact data.
169Select "Allow access" amd click "Yes" in this dialog.
170Now the importing is performed and KA/Pi will show a progress bar.
171After importing, KA/Pi shows a dialog, how much contacts are imported.
172If you press a second time "import" , already imported contacts are not imported again.
173After importing you can choose another "Contact Folder" to import or close the import dialog.
174Please close the import dialog.
175Now you see the imported contacts in KA/Pi on the left in the list view.
176Please verify, that the import was correct.
177About problems of mapping particular Outlook-data-fields to KAdressbook-data-fields see Appendix A).
178
179Choose menu:
180File - Save
181and close KA/Pi.
182Now you should have the contact data in the file std.vcf in your home directory in the path
183(YOURHOMEDIR)\kdepim\apps\kabc\std.vcf
184
185Copy that file to a moveable disk or memory stick or just copy it via network to the destination.
186Import that file into KAddressbook/Kontact via Import - Import vcard.
187Details about importing you can read at: 7) How to import your contact data into Kontact
188
189Now you have your Outlook200X contact data on the KDE desktop available and you are done with the migration of contacts.
190
191*************************************************************
1926) How to get the calendar data out of Outlook200X
193*************************************************************
194
195Note: When accessing Outlook to read the data, it should not be possible, that there is any data lost in Outlook, because the progam accesses Outlook only Read-Only.
196
197You have the file
198kopi.exe
199and the other needed files accessable on your workstation.
200
201Getting the calendar data
202
203NOTE: Before extracting the calendar data, it is recommended to extract the contact data first.
204If you extract the contact data first, the identity (UID) of attendees of a meeting can be mapped correctly in the newly created appointments, such that you can access the attendee contact data later directly from KOrganizer.
205
206Please start kopi.exe.
207
208You will see a dialog, that you started KO/Pi for the first time and that the timezone configuration will be shown now. Confirm with "Ok".
209
210Now you will see the configuration dialog of KO/Pi.
211Please choose your timezone and adjust the daylight saving settings.
212The dialog shows defaults for CET (Central European Time), such that users located in central Europe simply can press "OK" in that dialog.
213(Note: Don't forget to set the timezone in KDE KOrganizer before importing data there. The timezone in KDE KOrganizer is set per default to UTC (GMT), that is -1h of CET).
214
215Now you will see the KO/Pi main window.
216Choose menu:
217File - Import from OL
218You will get a dialog which shows all "Personal Folders" of Outlook.
219Choose the Calendar Folder(s) you want to import and select them with a hook.
220(All other folder but the calendar data containing folders are shown, but disabled).
221(If the data you want to import is not stored in one of the shown folders,
222please read step 2.) and click on "close" ).
223Click the "import" button.
224Now Outllok asks you to allow access to the contact data.
225Select "Allow access" amd click "Yes" in this dialog.
226Now the importing is performed and KO/Pi will show a progress bar.
227After importing, KO/Pi shows a dialog, how much calendar items are imported.
228If you press a second time "import" , already imported calendar items are not imported again.
229After importing you can choose another "Calendar Folder" to import or close the import dialog.
230Please close the import dialog.
231Now you see the imported calendar items in KO/Pi.
232Please verify, that the import was correct.
233About problems of mapping particular Outlook-data-fields to KOrganizer-data-fields see Appendix B).
234Close KO/Pi - data will be saved automatically.
235
236Now you should have the calendar data in the file mycalendar.ics in your home directory in the path
237(YOURHOMEDIR)\kdepim\apps\korganizer\mycalendar.ics
238
239Copy that file to a moveable disk or memory stick or just copy it via network to the destination.
240Import that file into KOrganizer/Kontact.
241Details about importing your calendar data you can read at: 8) How to import your calendar data into Kontact.
242(Warning again: Don't forget to set the timezone in KDE KOrganizer before importing data there. The timezone in KDE KOrganizer is set per default to UTC (GMT), that is -1h of CET).
243Now you have your Outlook200X calendar data on the KDE desktop available and you are done with the migration.
244
245Hint:
246If you want to use KO/Pi and KA/Pi on your windows desktop, you should read all the help information available in the KO/Pi Help menu. One Highlight of KO/Pi is the easy syncing with another *.ics file.
247(Information about syncing available in the KO/Pi help menu).
248Another hint:
249KO/Pi + KA/Pi ( = KDE-Pim/Pi ) are available for the Sharp Zaurus PDA.
250Syncing data works for KO/Pi ( version 1.9.3) but not yet for KA/Pi.
251
252
253*************************************************************
2547) How to import your contact data into Kontact
255*************************************************************
256
257We want to import and upload our contacts to a Kolab server.
258You should have access to a properly configured Kolab client.
259This Kolab client is Kontact in KDE.
260Make sure, you have the needed IMAP resources configured in KAddressbook.
261To configure IMAP resources, you should do:
262
263 Open KDE control center, choose there
264 KDE Components - KDE Resource Configuration
265 Choose there:
266 Resources: contact
267 and then:
268 Add...
269 IMAP
270
271Now start Kontact and select the Contacts icon on the left side.
272Choose menu:
273File... - Import - Import VCard...
274Select the imap resource as destination of the import
275and choose the file to import.
276Now the contacts should be imported and you are done.
277
278Don't forget to sync the IMAP account to upload to contacts to the server.
279
280*************************************************************
2818) How to import your calendar data into Kontact
282*************************************************************
283
284We want to import and upload our calendar data to a Kolab server.
285You should have access to a properly configured Kolab client.
286This Kolab client is Kontact in KDE.
287Make sure, you have the needed IMAP resources configured in KOrganizer.
288To configure IMAP resources, you should do:
289
290 Open KDE control center, choose there
291 KDE Components - KDE Resource Configuration
292 Choose there:
293 Resources: calendar
294 and then:
295 Add...
296 Calendar on IMAP-server via KMail
297
298Now start Kontact and select the Calendar icon on the left side.
299Choose menu:
300File... - Import - Merge Calendar...
301Select the imap resource as destination of the import
302and choose the file to import.
303Now the calendar data should be imported and you are done.
304
305Don't forget to sync the IMAP account to upload the calendar data to the server.
306
307*************************************************************
308APPENDIX A) Problems and solutions when reading contact data
309*************************************************************
310
311All data, which can be displayed and accessed in KAddressbook is imported from Outlook.
312In Outlook you can assign an attribute "This is the mailing address" to one of the addresses.
313This address shows up in KAddressbook twice.
314The first time with the original attribute from Outlook ( e.g. "work" for "business" in OL ).
315The second time with the attribute "postal".
316
317All telephone numbers of OL are imported.
318OL offers special case telephone numbers, like "Assistant", which have no counterpart in KAdressbook.
319In that case, the imported number has special combined attributes in KAddressbook.
320Here is the mapping of types in OL to attributes in KA:
321
322OL type Attributes in KA
323
324Assistant Work + Voice
325Business Work
326Business2 Work
327BusinessFax Work + Fax
328Car Car
329Home Home
330Home2 Home
331HomeFax Home + Fax
332ISDN Isdn
333Mobile Cell (displayed as Mobile Phone)
334OtherFax Fax
335OtherTelephone Voice
336Pager Pager
337PrimaryTelephone Pref ( displayed as typeless, with attribute preferred )
338TTYTDD Modem
339Telex Fax + Bbs (Bbs displayed as MailBox - not very senseful, sorry ...)
340CompanyMain Work + Pref
341Radio Video
342Callback Voice + Pref
343
344Some mapping may not be very senseful, but it helps to identify the original OL types.
345
346
347*************************************************************
348APPENDIX B) Problems and solutions when reading calendar data
349*************************************************************
350
351Almost all data, which can be displayed and accessed in KOrganizer is imported from Outlook.
352Attachments of appointments are not imported.
353KOrganizer may crash, when reading some kinds of attachments.
354These may be changed in future versions.
355
356Attendee lists of meetings and their state are imported in KOrganizer.
357
358A problem is importing some kinds of recurring events:
359
360First problem:
361OL offers a recurrence like
362- Yearly recurrence, every second Tuesday of July.
363KOrganizer ( in versions < 3.3.0 ) does not offer that kind of recurrence.
364Such that
365"Yearly recurrence, every second Tuesday of July."
366is converted to
367"Monthly recurrence, every 12. month, second Tuesday in month, StartMonth = July."
368which can be edited in KO.
369
370Second problem:
371OL offers an exception in a recurrence with other data/time.
372KO offers only an exception in a recurrence , where the exception is deleted from the row of all occurences.
373Such that
374"Recurring event with exception, that date XX should be at date YY"
375in OL is converted to two events in KO:
376"Recurring event with exception, that date XX is not included"
377"Non-recurring event at date YY with same data like the recurring event (e.g. Summary, location, attendee list, ...)"
378
379
380
381
382
383
384
385
386