Import2 will migrate your Posterous for FREE
Posterous, now part of Twitter, is closing down on April 30, 2013. Here is the official statement on their blog. This means that as of April 30, if you hosted a blog at Posterous it will no longer be available either to view or to edit. You have just few weeks to save your blog.
At Import2 we have decided to give a hand of help. Hand of free help. For next month Import2 premium data migration service from Posterous to Tumblr will be FREE (normally $49). All you need to do is claim your coupon below
(photo by Tammra McCauley)
January 16, 2013 at 7:34am
Introducing Import2 for Nimble
This week we are happy to welcome new member of our CRM data import tools family - Import2 for Nimble
But before telling about import tool, let me introduce Nimble itself. Nimble is a Social CRM, that in addition to standard CRM functionality helps to monitor your social stream and engage in relevant conversations with customers. Just in case you are wondering what is Social CRM, I have included excerpt of a blog by Jon Ferrara (founder of Nimble) giving some explanations:
“Social CRM is achieved by blending the power of CRM, i.e. managing and nurturing customer interactions, with the benefits of Social Media, i.e. listening and engaging, to create deeper, more trusted relationships with your prospects and customers.”
Starting today all Nimble users can enjoy simple and reliable data import service. It will help to easily import your contacts, accounts and corresponding sales history from your existing CRM into Nimble. And as all Import2 tools it’s as easy as clicking one button.
Start 1-click migration now.
August 10, 2012 at 8:47pm
Import2 News: SugarCRM to Salesforce migration
Import2 vision is to make switching software quick and easy. It’s a hard problem to solve, but we are moving one step at a time. And today I am happy to share the news that we are adding new member to Import2 migration tools family: SugarCRM to Salesforce
As with Highrise to Salesforce, it will help you bring your data Into Salesforce quickly and easily. No Scripts, No Mappings, No Hassle!
Here’s how it works: You authenticate with your Sugar CRM and Salesforce accounts and press big “Start Import” button. Right after that Import2 automatically downloads all contacts, accounts, leads and opportunities from SugarCRM and immediately moves them into Salesforce.
Give it a free try or let us know if you have any questions about Import2
Building API Limit Conscious Salesforce Apps
Salesforce API is well known for strict usage limitations. Customer is given 1,000 API requests per day for each user license. Having this limit to be shared among all the customers 3rd party apps, it’s no surprise that hitting the limits is one of the common issues for app developers.
- By default Group and Professional Edition customers don’t have API enabled. Thought you can turn on the API on Professional Edition for an additional fee.
- Aloha apps, are the apps by Salesforce partners who passed security review and allowed to access Group and Professional Edition API even if it’s not turned on for the organization.
- Bulk API is available only for Enterprise and Unlimited customers and you can’t turn it on even for money.
- Enterprise Edition customers are given 1,000 request per day for each user license.
SOAP API is Mini-Bulk API
Interesting finding we have made last week - app can add up to 200 records in a single create() SOAP call. So if your app is like Import2, doing lot’s of create calls, you can bulk those into single API call. It helped us decrease number of API calls by 50%.
If SOAP API hack doesn’t help, then Bulk API is the way to go. It’s an asynchronous REST API and will allow you great flexibility. Though, you have to be at least on Enterprise Edition to use Bulk API.
Overall Salesforce has the tools you need to build app that doesn’t hit API limits. Only question I have is whether it would make more sense for Salesforce to provide consistent across various editions and less restrictive API usage limits?
What Can Go Wrong With Data Migration
I wish somebody has written this blog post before we have started our first data migration.
(Photo by origamidon)
As you may guess, there are millions of things that can possibly go wrong when you are migrating the data between software systems. Here I wanted to highlight the things that are most common to happen and that you can quickly take actions against:
- You can’t access old system. It often happens when administrator turns off access to old software too early. Or if you are using Software as a Service your subscription expires before you have a chance to migrate all the data. Be sure to check your subscriptions and user access rights ahead of the time.
- Duplicate records. If you initiate import script several times, as a result you will find lot’s of duplicate records in your system that you need to clean up. So either double check not to create dublicate records or find your self data cleansing tool.
- Your export file is too large. For example, if you are using CSV files for export/import and your database is just so huge that opening CSV file in office tool becomes impossible.
- Missing records. Watch out for error messages provided by your migration tool. There might be important notifications about some records that were not imported. If that’s the case make sure your review each case carefully and import those afterwords manually.
- Missing field values. Sometimes because of the wrong tool configuration you can find out that some fields are not being imported. Easiest is to take couple of imported records and go through each field in details to find out if something is not being moved over.
- Users continue to going to old system. Changing the habits is extremely hard. So often, after you have setup new system and migrated data users will be still going into old system and update the information there. Makes sure, that you limit access to old system at correct time.
It’s better to understand what can go wrong before you start. Allows you to be prepared for the worst case scenario.
Salesforce API Usage Limit
Salesforce AppExchange has more than 1,500 apps listed, consumer products like Facebook and Twitter count hundreeds of thousands if not million apps on their platforms. Making API a great opportunity for 3rd party developers to extend functionality of cloud applications.
But it doesn’t come without limitations.
(Photo by jpctalbot)
Last week when migrating CRM data for one of our customers, Import2 has crashed with error message ”TotalRequests Limit exceeded”. So we had to do our homework and researched everything related to API usage limits and possibilities how to increase those. Here is a quick overview of what we have learned about Salesforce API usage limits:
- If you want to check your current API usage status go to Your Name | Setup | Company Profile | Company Information
- All limits are calculated over 24 hours period are applicable to whole organization. So if you have several users connecting through API all of them work against the same limit.
- You get 1,000 API requests per each Salesforce user. Even Unlimited Editions is actually limited to 5,000. Here is a detailed API limits overview.
- You can purchase additional API calls, though I am not sure what’s the cost. It was faster to wait 24 hours.
3 Tools to Import Data Into Salesforce
Understanding Salesforce Audit Fields
Wish importing data to Salesforce would be easy. Today I want to give a quick overview on an aspect that bothers us almost in any Salesforce import we do - Audit Fields.
Here is the list of all Audit Fields you may need:
- CreatedById - user who created the record;
- CreatedDate - time when this record was created;
- LastModifiedById - user who last updated this record;
- LastModifiedDate - time when this record was last modified by a user.
All of those fields are updated automatically by Salesforce when you create or modify records using UI. But, what if youwant to migrate the data from old CRM and wish to manually updated those fields.
NB! By default Salesforce.com doesn’t allow you to update Audit Fields
What you need to do is contact Salesforce.com support and ask to enable updating the audit fields. Salesforce typically will come back to you with bunch of questions and once they enable this capability for your organization, values of audit fields will be editable.
If you want to learn more - Salesforce documentation about audit fields
10 Checkpoints to Validate Your Salesforce Data Import
So you have just completed your CRM data import into Salesforce and want to make sure everything went right. I wanted to share a checklist that we use at Import2/Salesforce when validating the results of Salesforce data migration
- Count number of accounts, contacts, leads and opportunities and check if it matches the amount you have exported from old CRM.
- Next look at several accounts, contacts, leads and opportunities to see if fields are there.
- Look at phone number. Are US number formatted correctly, international numbers. Did you lose extensions?
- Address. Did both Billing and Mailing address fields are complete. If yes, look at the address of any account or contact and make sure all fields (street address, city, state, zip code, country) is present
- Were notes imported correctly? Pay attention to encoding in different languages if you have those.
- If in your previous CRM you had contacts without associated companies did they appear at Salesforce?
- Same with opportunities. If in your previous CRM you had opportunities without associated companies, did they appear at Salesforce?
- Check values of system fields: owner, created date, last modified by, last modified date
- Custom fields. If you used custom fields in your old CRM, now make sure each of these fields has corresponding field at Salesforce
- If you were importing users too, do you have same amount of users in Salesforce? Did their names and emails were correctly assigned?
Btw, if you have bunch of hidden fields Force.com Explorer might help you to query the data right from the Salesforce database.