Bring the products registered on your webCRM customers across

webCRM keeps two different lists that both get called products. One is your price list. The other is the list of things a particular customer has: the firewalls, the licences, the service agreements, each one sitting on a company with its own serial number, start date and end date. This page is about the second one.

That second list is yours, not webCRM's. You chose how many fields it has, what each one is called and what goes in it, so no two accounts look alike. The import reads your setup first and builds a matching object in DealJourney before it moves a single record.

What you get

Choose Customer products in the webCRM sync and it creates an object called Products, with one field for every field you configured in webCRM. Your names carry over exactly: a field you called Serienummer is called Serienummer here too, in your own language.

The types carry over as well, so the fields behave rather than just holding text. A date stays a date and can be filtered on. A dropdown keeps its list of choices. A price becomes a number you can sort by.

Every record is attached to the customer it belongs to, so it shows up on that customer alongside everything else about them. If the record also names a contact person in webCRM, that link comes across too.

Anything you typed as a free remark in webCRM arrives as a note on the record's timeline, which is where people look for that kind of thing, rather than being buried in a form field.

If you already built the object yourself

Some people built the shell by hand before this existed: an object with the right fields, waiting to be filled. The import can fill that one instead of standing up a second list beside it, as long as the field names match what you called them in webCRM.

It leaves your object alone in every other respect. A field you made a free-text box stays a free-text box even where webCRM calls it a price, and the value arrives in the shape your field expects. Only a webCRM field you never built gets added.

If the import is about to create its own object and finds one of yours that already holds the same fields, it says so in the run summary rather than quietly making a second one.

Running it more than once

Run it as often as you like. Each record remembers which webCRM record it came from, so a second run updates what is already here instead of creating a second copy of your whole list. The same is true of the notes.

Renaming a field in webCRM is safe: the new name appears here and nothing you have already imported is lost.

What it tells you afterwards

The run reports what arrived and what did not, which is worth a look the first time:

• Records whose company is not in DealJourney yet are counted. This normally means the customer import has not been run, or was run before that company existed in webCRM. Sync organisations, then run this again and they find their customer.
• Any webCRM field that did not become a field here is listed with the reason. Most of them are webCRM's own housekeeping, such as its change log and its created and changed stamps, which DealJourney keeps itself.
• A field you configured in webCRM but never gave a name is listed too. There is no sensible column to make out of an unnamed field, so it is reported rather than guessed at.

Nothing is dropped quietly. If a column you care about is not here, it is named in that list with the reason.

Working with them afterwards

From that point they behave like any other object in DealJourney: the same filters, saved views, columns and export. See Custom objects. You can rename a field, hide one you do not need, or add one of your own, and the next sync will not undo it.