Bring your webCRM files across

The webCRM sync brings your customers, contacts, deals and activities. The files saved on those webCRM records are a separate step, because there are usually a lot of them and they take a while to move.

Connect somewhere to keep them first. The files are stored in your own storage, not inside DealJourney, so you need OneDrive, SharePoint, Google Drive or Dropbox connected before anything can move. See Connect SharePoint. Until one is connected the page says so and the import button stays off.

Move them across

1. 1Open the webCRM integration and go to its Gemte filer og dokumenter tab.
2. 2Press Gennemsøg webCRM. Læser listen over dokumenter i webCRM og finder ud af, hvilken DealJourney-post hver fil hører til. Intet bliver downloadet, så det går hurtigt og kan gentages.
3. 3When the scan finishes you get a count and a total size. This is the moment to check the number looks like what you expect.
4. 4Press Importer filer. Downloader hver fil fra webCRM og gemmer den på dens post. Den kører i hold og fortsætter, hvor den slap, så du kan stoppe og starte, når du vil.

Leave the tab open while it runs. If you close it, or press Pause, nothing is lost: press Importer filer again later and it carries on from where it stopped. Running the whole thing twice does not create duplicates either, because every file is remembered by its webCRM id.

Where each file ends up

A file goes onto the record it was attached to in webCRM:

• A file on a webCRM organisation lands På kunden.
• A file on a webCRM delivery or opportunity lands På handlen. Most contracts and order confirmations are these.
• A file on a webCRM person lands På kontakten.
• A file on a webCRM activity or meeting lands På aktiviteten.

You then find it the same way as any other file on that record. See Record folders.

What gets skipped, and why

De oversprungne filer er kalenderinvitationer og anden webCRM-oprydning uden en DealJourney-post at ligge på. Intet går tabt; de har bare ingen naturlig plads.

A skipped file is counted and listed, never silently dropped. If the count looks too high, it usually means part of the webCRM sync has not run yet: finish importing the records first, then scan again and the files that had nowhere to go will find their record.

If some files fail

Individual files can fail — a storage quota, a token that expired mid-run, a file webCRM will not serve. They are listed with the reason under Filer der ikke kom over, and Prøv disse igen puts them back in the queue. Everything that already came across is untouched.

If the whole batch stops early, that is deliberate: several files failing in a row means something is wrong for all of them, and it is better to stop and show you than to grind through thousands of failures.