Tag Archives: Migrate

How to Migrate Salesforce.com Attachments to Dynamics 365

useeeee 300x225 How to Migrate Salesforce.com Attachments to Dynamics 365

In order to migrate attachments from Salesforce to Dynamics CRM, we could use Kingswaysoft without writing any code through the Developer version.

Kingswaysoft has a premium Derived column tool available that decodes the Attachment encoded string from Salesforce.com and migrates it to Dynamics 365. The license needs to be obtained only to use the SSIS package in production as a scheduled job or through the command line tool.

The process is explained as below:

  1. Download the Kingswaysoft Productivity tools here.
  2. Once it is installed, reopen the Visual studio and the Premium tools should appear in the SSIS toolbox as below.

082917 2058 HowtoMigrat1 How to Migrate Salesforce.com Attachments to Dynamics 365

  1. Drag and drop the Premium Derived Column to the DataFlow.
  2. Use the DecodeBase64 function and use the field where the attachment is stored. In the below case, it is the field Body from Salesforce.com.

082917 2058 HowtoMigrat2 How to Migrate Salesforce.com Attachments to Dynamics 365

  1. Make sure the DataType is DT_Image, which will be automatically populated.
  2. Run the SSIS package after mapping the column with the documentbody field in Annotation entity in Dynamics 365.
  3. Verify by opening the document/pdf from the associated entity (example case or opportunity or quote). The PDF will open in CRM with the same contents as in Salesforce.com.

Voila! You’ve migrated your Salesforce.com attachments Dynamics 365!

Happy Dynamics 365’ing!

Let’s block ads! (Why?)

PowerObjects- Bringing Focus to Dynamics CRM

MediaTek Takes Hit As Chinese Smartphones Migrate To Qualcomm

The financial report from Taiwan-based semiconductor firm MediaTek for the second quarter of 2017 shows the company’s net profit declined over 60%.

MediaTek’s operating revenue in the second quarter of 2017 was NTD58.079 billion, which was about CNY12.912 billion and marked a year-on-year decrease of 19.9%. Its net profit was NTD2.21 billion, which was about CNY491 million and marked a year-on-year decrease of 66.5%. The company’s performance reportedly hit a new quarterly low point since its listing.

As a major IC designer focusing on smartphone chips, MediaTek’s smartphone business operating revenue only accounted for 40% of the company’s total operating revenue during the reporting period.

With Qualcomm’s enhancement in the middle- and low-end markets, MediaTek’s former major clients Oppo and Vivo have reportedly turned to Qualcomm starting at the end of 2016. This cost MediaTek many orders. Though Meizu recently used MediaTek’s HelioX30 on its PRO7 smartphone, it still cannot make up the Taiwanese company’s sales losses in the high-end market.

Let’s block ads! (Why?)

ChinaWirelessNews.com

How to Bulk Migrate Dynamics CRM Licences to Dynamics 365 Licences using PowerShell

Along with the rename of Dynamics CRM to Dynamics 365 came new licenses. If you’re on Office 365 with the old Dynamics CRM licenses being assigned to users you will need to re-assign Dynamics 365 licenses to these users at some point.

If you have tens of users then manually removing and assigning the new Dynamics 365 licenses will be just fine. But if you have hundreds or thousands, you probably don’t want to spend a weekend manually doing this. So, here is a little PowerShell script that will do the heavy lifting.

$  credentials = Get-Credential
Connect-MsolService -Credential $  credentials

Get-MsolAccountSku
Get-MsolAccountSku | Format-Table AccountSkuId, SkuPartNumber

$  myplan = New-MsolLicenseOptions -AccountSkuId "tenant:DYN365_ENTERPRISE_TEAM_MEMBERS" -DisabledPlans SHAREPOINTENTERPRISE,SHAREPOINTWAC,PROJECT_ESSENTIALS

Set-MsolUserLicense -UserPrincipalName "user@user.com" -AddLicenses "tenant:DYN365_ENTERPRISE_TEAM_MEMBERS" -LicenseOptions $  myplan

Set-MsolUserLicense -UserPrincipalName "user@user.com" -RemoveLicenses "tenant:CRMPLAN2"

The first two lines will ask for credentials of your Office 365 tenant.

Get-MsolAccountSku will list out your current licenses, this is needed to find the exact name of the “tenant” which will be used when adding  and removing the existing Dynamics CRM licenses.

Basically, what’s required is to create a custom plan by removing the SharePoint and Project sub-plans, these are already part of other O365 plans such as E1. If you don’t remove these, the PowerShell command will fail stating that the sub-plans are already assigned to this user.

Once $ myplan is configured with the required license, in this example it’s the Dynamics 365 Enterprise Team Member license you can run Set-MsolUserLicense –AddLicenses command.

The last thing to do is to remove the existing Dynamics CRM license. e.g. CRMPLAN2

To run this over multiple users you can foreach loop users from Office 365, this can also be retrieved using PowerShell but I’ll leave that to you to figure out, can’t make it too easy wlEmoticon smile 2 How to Bulk Migrate Dynamics CRM Licences to Dynamics 365 Licences using PowerShell

Let’s block ads! (Why?)

Magnetism Solutions Dynamics CRM Blog

Ready to Migrate ESPs? Here’s Your Email Deliverability Checklist

Migrating ESPs Your Email Deliverability Checklist FI Ready to Migrate ESPs? Here’s Your Email Deliverability Checklist

This article focuses exclusively on the deliverability components you should be aware of in order to be successful in your migration to a new ESP.

Suppression Lists

At Act-On, we classify suppression lists into:

  • opt outs
  • spam complaints
  • hard bounces
  • inactive soft bounces (soft bounces that exceed a certain threshold and are considered undeliverable)

Understanding the differences between hard and soft bounces can be confusing if you’re not in the trenches with your email deliverability team. Traditionally, a “hard bounce” indicates a permanent reason an email cannot be delivered. The usual reasons are an invalid email or an invalid domain.

“Soft bounces” have been defined as temporary failures due to an unavailable server, a full mailbox, or an oversize message. While those causes still hold true in theory, they no longer represent the top reasons behind today’s soft bounces, which are mostly caused by internet service provider (ISP) blocks. In most cases the blocks are temporary and can often be resolved by identifying the root causes, then following email best practices and ISP guidelines. Read our post Understanding and Reducing Soft Bounces to better understand how to identify and fix soft bounces.

Your email service provider might classify them differently, or might not classify them at all. Whatever the case, these are contacts that must be uploaded into your new account and suppressed, as they either don’t want to receive email from you or are simply undeliverable addresses. Not properly suppressing these contacts will start you off on the wrong foot and cause your reputation with the new ESP (and your customers and prospects) to quickly suffer.

Engagement Data

If you decide to use a dedicated IP with your new ESP, being able to identify and migrate over your engaged recipients will help establish a good IP reputation. By sending to your most engaged contacts from the new IP during the initial warm-up period, you can show ISPs that you are sending to people who want your email, and thus may have less of a chance of being blocked or labeled as a poor sender.

“From” Domains

When you bring your old sending domains with you, be aware you are carrying over the good – or bad – sender reputation you’ve established over the years. Despite the fact that changing domains is a spammer’s practice and highly discouraged, a new “From” domain does allow you to start fresh with a clean slate and gives you a second chance to be a good sender moving forward.

Data Hygiene

Though not a prerequisite for an ESP migration, practicing good data hygiene can go a long way toward ensuring your onboarding is as smooth as possible. A list cleanse is recommended every six months or so to help keep your list as clean as possible. Most ESPs have their own database of bad and risky contacts to suppress against globally, so just because you weren’t running into issues with the previous ESP doesn’t mean the issues weren’t there.

Embracing list maintenance best practices ensures you get optimal deliverability and performance on your campaigns. Here are some tips for measuring how clean your email list is.

Authentication

Email authentication is an integral part of your infrastructure for mass mailing. Make sure Domain Name System validation (DKIM) and Sender Policy Framework (SPF) are properly set up at the corresponding domains with the new ESP, as your old setups will not migrate over.

Whitelisting

To ensure successful delivery of test and live messages from the new platform to your internal servers, you may need to whitelist your new sending IP(s) and domain(s) to prevent potential hiccups.

Whitelisting is the opposite of blacklisting. It lets your email service provider know that you are a willing recipient of the emails sent from that IP address.

Check out our post on common terms for the email marketer, parts one and two.

Transitioning

Last but not least, while we understand you expect a lot more from the new partnership, transient deliverability problems can occur during the warm-up process. You may experience temporary blocks by ISPs and dips in your engagement rates. This is normal for any new IPs and/or domains you are trying to build up.

To help speed up the process and minimize the time needed for the transition, we recommend fully migrating to the new ESP from the get-go and refraining from using both the old and new ESPs simultaneously, a behavior that exhibits similarity to snowshoe spamming (a spammer’s strategy for pushing spam over multiple domains and IP addresses – spreading out the weight – to avoid filters).

Conclusion

And remember, a new ESP shouldn’t replace email marketing best practices such as A/B testing your subject lines and other components of your email, segmenting your lists, and being thoughtful about your sending schedules. More tips on improving your deliverability and open rates can be found on our post The Blame Game : Open Rates vs Deliverability.

Let’s block ads! (Why?)

Act-On Marketing Action Blog

Migrate Closed Microsoft CRM Opportunities using SSIS Integration Toolkit

Recently I did a data migration from Microsoft Dynamics CRM On-Premise to CRM Online using the SSIS integration toolkit. This tool is useful for migrating data between CRM instances without needing to export everything into Excel spread-sheets or write a console application.

While migrating opportunities between my CRM instances, I had to migrate several closed opportunities and because these were closed an “Opportunity Close” record was created automatically for them. However, this record did not contain an Actual End Date which is some information I needed to keep. So I wanted to remove these records from the destination system and copy my existing ones over.

Here’s what I did:

image thumb Migrate Closed Microsoft CRM Opportunities using SSIS Integration Toolkit

First we want to remove only those Opportunity Close records that don’t contain an Actual End Date value (in the destination system). In the toolkit you are given the option of either using an entity or a FetchXML query as the source type. Use FetchXML as you can specify the selection criteria to take only those records which don’t contain data for their Actual End Date value.

image thumb 1 Migrate Closed Microsoft CRM Opportunities using SSIS Integration Toolkit


<fetch mapping=’logical’> <entity name=’opportunityclose’> <attribute name=”subject” /> <filter type=”and”> <condition attribute=”actualend” operator=”null” /> </filter> </entity></fetch>

We are going to delete these entities so use the Delete action in the destination.

image thumb 3 Migrate Closed Microsoft CRM Opportunities using SSIS Integration Toolkit

NOTE: When performing the Delete action, the Connection Managers we configure need to be the same. This is because we are not moving data from one system to another, but editing the content that’s already there.

Next we migrate the correct data, this time using entity as the Source Type. The Connection Managers in this step will need to be different, that is, one pointing to the source system and the other pointing to the destination system.

image thumb 4 Migrate Closed Microsoft CRM Opportunities using SSIS Integration Toolkit

This action will be performed as a Create. This is because we know that there is no matching Opportunity Record in the destination system, and also Opportunity Close records cannot be updated.

image thumb 5 Migrate Closed Microsoft CRM Opportunities using SSIS Integration Toolkit

Just to be safe, you can change the error-handling mechanism to ignore any errors. For example, an Opportunity Close record might already exist in the destination system because it has an Actual End value, so there is no need to change this record.image thumb 6 Migrate Closed Microsoft CRM Opportunities using SSIS Integration Toolkit

Incorporate these steps into your process the next time you need to migrate closed Opportunities from one CRM system to another. This will ensure that your data is accurate.

This entry passed through the Full-Text RSS service – if this is your content and you’re reading it on someone else’s site, please read the FAQ at fivefilters.org/content-only/faq.php#publishers.

Magnetism Solutions Dynamics CRM Blog

Migrate Closed Microsoft CRM Opportunities using SSIS Integration Toolkit

Recently I did a data migration from Microsoft Dynamics CRM On-Premise to CRM Online using the SSIS integration toolkit. This tool is useful for migrating data between CRM instances without needing to export everything into Excel spread-sheets or write a console application.

While migrating opportunities between my CRM instances, I had to migrate several closed opportunities and because these were closed an “Opportunity Close” record was created automatically for them. However, this record did not contain an Actual End Date which is some information I needed to keep. So I wanted to remove these records from the destination system and copy my existing ones over.

Here’s what I did:

image thumb Migrate Closed Microsoft CRM Opportunities using SSIS Integration Toolkit

First we want to remove only those Opportunity Close records that don’t contain an Actual End Date value (in the destination system). In the toolkit you are given the option of either using an entity or a FetchXML query as the source type. Use FetchXML as you can specify the selection criteria to take only those records which don’t contain data for their Actual End Date value.

image thumb 1 Migrate Closed Microsoft CRM Opportunities using SSIS Integration Toolkit


<fetch mapping=’logical’> <entity name=’opportunityclose’> <attribute name=”subject” /> <filter type=”and”> <condition attribute=”actualend” operator=”null” /> </filter> </entity></fetch>

We are going to delete these entities so use the Delete action in the destination.

image thumb 3 Migrate Closed Microsoft CRM Opportunities using SSIS Integration Toolkit

NOTE: When performing the Delete action, the Connection Managers we configure need to be the same. This is because we are not moving data from one system to another, but editing the content that’s already there.

Next we migrate the correct data, this time using entity as the Source Type. The Connection Managers in this step will need to be different, that is, one pointing to the source system and the other pointing to the destination system.

image thumb 4 Migrate Closed Microsoft CRM Opportunities using SSIS Integration Toolkit

This action will be performed as a Create. This is because we know that there is no matching Opportunity Record in the destination system, and also Opportunity Close records cannot be updated.

image thumb 5 Migrate Closed Microsoft CRM Opportunities using SSIS Integration Toolkit

Just to be safe, you can change the error-handling mechanism to ignore any errors. For example, an Opportunity Close record might already exist in the destination system because it has an Actual End value, so there is no need to change this record.image thumb 6 Migrate Closed Microsoft CRM Opportunities using SSIS Integration Toolkit

Incorporate these steps into your process the next time you need to migrate closed Opportunities from one CRM system to another. This will ensure that your data is accurate.

This entry passed through the Full-Text RSS service – if this is your content and you’re reading it on someone else’s site, please read the FAQ at fivefilters.org/content-only/faq.php#publishers.

Magnetism Solutions Dynamics CRM Blog