Last updated: 2025-12-02
SmartResource for Carrier-Plan Data - Realigning Local Office Content
SmartResource for Carrier-Plan Data - Realigning Local Office Content
)
The link for this help topic is:
In this Topic ShowHide)
- Overview
](javascript:void(0);)
Overview
Note: This feature is not
available in Canada and Australia.
Many agency offices that establish a new [SmartResource
for Carrier-Plan Data](/help/pro/smartresource/for/carrier-plan/data/-/introduction) subscription have existing carrier records that
they created locally in SmartOffice.
If a carrier in the local office exists in the resource office, the
local carrier record and its associated products can be realigned to point
to their corresponding resource office records. The Carrier Migration
and Product Migration utilities serve this purpose.
When the realignment is complete, local office content such as
carrier contact information, agent contracts and appointments, policies
and pending cases are linked to the appropriate resource office carriers.
Carrier Migration
Watch the Training Class:
[Carrier
Migration](https://help.smartofficecrm.com/movies/carrier_migration_flash/carrier_migration.html)
The Carrier Migration utility is the main utility used to realign local
office content.
-
[Search
for the Dynamic Report](/help/pro/dynamic/reports/-/searching/for/dynamic/reports) named Carriers
and Products Only, No Riders – Detail.
-
[Run
the report](/help/pro/dynamic/reports/-/running/a/dynamic/report) to display a list of carriers and products in the resource
office.
-
the report results](/help/pro/lists/-/exporting/a/list).
-
[Perform
a blank carrier search](/help/pro/insurance/carriers/-/searching/for/carriers) to display a list of all carriers. The
list of results includes both local carrier records and resource office
carriers (the latter are highlighted in blue and are read-only).
-
Ensure that the names of local carriers
and their products match exactly with those in the Dynamic Report.
Rename any local carrier or product names that do not match.
Note: Local product records that
are not in the resource office (i.e., historical products) do
not have to be renamed. These products remain in the local office
with their policies still attached, but the products are re-pointed
to the appropriate carrier in the resource office.
-
Perform the following steps one carrier
at a time:
a local carrier and the corresponding resource office carrier.
-
Select Menu
> Carrier Migration.
-
When the confirmation message
displays, click the Yes
button.
Performing these steps produces these results:
-
All local office content associated
with the carrier is switched to the resource carrier of the same name.
The same is true of any products in the local office.
-
Successfully matched local office carriers
and products are not deleted. They are renamed with an "X_"
prefix and are left in the local office for review. These records
no longer have any useful content associated with them and have also
been coded as NO PCM Activity. They can be deleted at any time.
-
Active products that remain in the
local office are not renamed. These products remain active but are
realigned with the resource office carrier instead of the local office
carrier.
Product Migration
Normally, all of a carrier's products are migrated along with their
carriers when the Carrier Migration utility is run. Under some circumstances,
however, a product may not be migrated during carrier migration (e.g.,
if the product was not renamed properly). These products can be migrated
individually using the Product Migration utility.
Perform the following steps on one product at a time:
-
[Perform
a blank product search](/help/pro/products/-/searching/for/products) to display a list of all products. The
list of results includes both local product records and resource office
products (the latter are highlighted in blue and are read-only).
-
Ensure that the local product's name
matches exactly with the corresponding product in the resource office
(refer to the Dynamic Report created during the carrier migration
process). If necessary, rename the local product.
-
the local product and the corresponding resource office product.
-
Select Menu
> Product Migration.
-
When the confirmation message displays,
click the Yes button.
Rider Migration
Normally, all of a carrier's riders are migrated along with their carriers
when the Carrier Migration utility is run. Under some circumstances, however,
a rider may not be migrated during carrier migration (e.g., if the rider
was not renamed properly). These riders can be migrated individually using
the Rider Migration utility.
Perform the following steps on one rider at a time:
-
From the SmartOffice side menu, select
Insurance > Riders
to open the Search Riders dialog box.
-
Click the Search
button to display a list of all riders. The list of results includes
both local rider records and resource office riders (the latter are
highlighted in blue and are read-only).
-
Ensure that the local rider's name
matches exactly with the corresponding rider in the resource office.
If necessary, rename the local rider.
-
the local rider and the corresponding resource office rider.
-
Select Menu
> Rider Migration.
-
When the confirmation message displays,
click the Yes button.
Service Provider Migration
Service providers from the local office can be realigned to point to
their resource office equivalents using the Service Provider Migration
utility.
Perform the following steps on one service provider at a time:
-
[Perform
a blank service provider search](/help/pro/pending/cases/-/searching/in/smartcasemanager) to display a list of all service
providers. The list of results includes both local service provider
records and resource office service providers (the latter are highlighted
in blue and are read-only).
-
Ensure that the local service provider's
name matches exactly with the corresponding service provider in the
resource office. If necessary, rename the local service provider.
-
the local service provider and the corresponding resource office service
provider.
-
Select Menu
> Service Provider Migration.
-
When the confirmation message displays,
click the Yes button.
](javascript:void(0);)